From: Larry W. V. <lv...@ca...> - 2001-03-06 15:51:28
|
With the previous release of pilot-db utilities, pdb2csv took these arguments: usage: pdb2csv.prev [options] PDB_FILE CSV_FILE INFO_FILE -e, --extended Output records using extended CSV mode -h, --help Display this help screen -v, --version Display program version -m, --mobiledb Force PDB to be read in MobileDB-format. -d, --db Force PDB to be read in DB-format. -n FILE --errors=FILE Send all error messages to FILE The latest version says this: usage: pdb2csv [options] PDB_FILE CSV_FILE INFO_FILE -e, --extended Use extended CSV mode. -s SEP, --separator=SEP Change the default field separator. (Default: ",") -h, --help Display this help screen. -v, --version Display the program version. -n FILE, --errors=FILE Send all error messages to FILE. -d FORMAT, --date=FORMAT Change the output format for date fields. -t FORMAT, --time=FORMAT Change the output format for time fields. -D FORMAT, --datetime=FORMAT Change the output format for datetime fields. 1. The fact that -d used to mean one thing, and now means another, is really unfortunate, as it leaves user scripts doing things not intended. 2. The fact that -d is used by csv2pdb to indicate the type of pdb to generate, and by pdb2csv to mean something else is unfortunately,l inconsistency tends to result in user error. 3. Question - how DO I indicate what type of pdb is being read? -- Never apply a Star Trek solution to a Babylon 5 problem. Larry W. Virden <mailto:lv...@ca...> <URL: http://www.purl.org/NET/lvirden/> Even if explicitly stated to the contrary, nothing in this posting should be construed as representing my employer's opinions. -><- |