Changeset 4359 for trunk/glueforge/glueforge.in
- Timestamp:
- Jun 22, 2005, 3:56:56 PM (21 years ago)
- File:
-
- 1 edited
-
trunk/glueforge/glueforge.in (modified) (4 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/glueforge/glueforge.in
r4358 r4359 3 3 # Copyright (C) 2005 Joshua Hoblitt 4 4 # 5 # $Id: glueforge.in,v 1.2 5 2005-06-23 01:34:31jhoblitt Exp $5 # $Id: glueforge.in,v 1.26 2005-06-23 01:56:56 jhoblitt Exp $ 6 6 7 7 use strict; … … 190 190 =head1 SYNOPSIS 191 191 192 md2db.pl --input <filename> [--output < filename>] [--template <dirname>]192 md2db.pl --input <filename> [--output <dirname>] [--template <dirname>] 193 193 194 194 =head1 DESCRIPTION 195 195 196 This program generates a set table description specific database bindings. The197 code generated is larger just wrapper functions around the C<pslib> C<DB> API. 198 The table description is read in from a file in the C<Metadata Config File> 199 format.196 This program generates a set of database table specific bindings in the ANSI C 197 language. The code generated is largely just wrapper functions around the 198 C<pslib> C<DB> API. A simple table description is read in and a directory 199 containing a complete, distributable software package is created. 200 200 201 201 =head2 Features … … 213 213 =item * Builds both shared and static libraries by default. 214 214 215 =item * Generates man pages and HTML documentation with doxygen.215 =item * Generates man pages and HTML documentation with Doxygen. 216 216 217 217 =item * Header files should be C++ safe. 218 218 219 =item * Functions to open and close database connections. 220 221 =item * Functions to create and destroy a table of the appropriate format. 222 223 =item * Functions to insert and pop a row. 224 225 =item * Functions to insert and pop a simple object representing a row. 226 227 =item * Functions to insert, select, and pop to/from FITS files. 228 229 =item * Functions to convert between row structs and C<psMetadata>s. 230 219 231 =back 220 232 221 =head1 CONFIG FILE FORMAT 222 223 Configuration files specify the name of the table, the name and types of all 224 columns, and can optional specify which column are to be used as indexes. 233 =head1 TABLE DESCRIPTION FORMAT 234 235 A simple config files specifies the name of the table, the name and types of 236 all columns, and can optional specify which column are to be used as indexes. 237 These C<Table Description> files are in the C<Configuration files> format as 238 described in C<PSDC-430-007>. 225 239 226 240 =head2 Example table description … … 233 247 zot BOOL t # Key 234 248 249 The key name C<table> is reserved and specifies the name of the database table. 250 It may appear any where in the file but it is most I<convenient> to have it as 251 the first line of the table description. 252 253 The value of a C<STR> column specifies the maximum number of characters that 254 the database is required to store for that field. The values for C<S32>, 255 C<F32>, C<F64>, & C<BOOL> columns are ignored. 256 257 Keys maybe specified as a C<Primary Key> or C<Key>. Only one C<Primary Key> 258 may be specified per table. 259 260 The key name C<position> is also reserved as it is used internally by the 261 database bindings. 262 235 263 =head1 OPTIONS 236 264
Note:
See TracChangeset
for help on using the changeset viewer.
