|-c||Generate a CREATE TABLE statement to make a table with similar datatypes and column names as the DBF file. Default.|
|-C||Suppress the CREATE TABLE statement.|
|-d||Generate a DROP TABLE statement before the CREATE TABLE statement. This is useful for replacing the contents of a table that already exists in PostgreSQL. Default.|
|-D||Suppress the DROP TABLE statement.|
|-e||Change the DROP TABLE statement to DROP TABLE IF EXISTS so that newer versions of PostgreSQL (8.2+) will only attempt to drop the table if its already defined. PostgreSQL will return an error when attempting to drop a table that does not exist unless IF EXISTS is used. Default.|
|-E||Do not use the IF EXISTS modifier to DROP TABLE for compatibility with versions of PostgreSQL older than 8.2.|
|-h||Print a help message, then exit.|
|The name of the associated memo file (if necessary).|
|-n||Create NUMERIC fields with type NUMERIC. Default.|
|-N||Create NUMERIC fields with type TEXT. Use this if rows contain invalid number data in NUMERIC fields (which are essentially CHARACTER fields behind the scenes).|
|-p||Show a progress bar during the conversion process.|
|-P||Do not show a progress bar. Default.|
|-q||Enclose the name of the table in quotation marks in statements like "CREATE TABLE", "DROP TABLE", and so on. This is useful in cases where the table name is a PostgreSQL reserved word, and almost certainly harmless in all other cases.|
|-Q||Do not enclose the name of the table in quotation marks. Default.|
|Set the encoding used in the input file. When given, output will be converted from that encoding to UTF-8. Supported encodings depend on your version of the iconv library. Available only if your copy of PgDBF was compiled with iconv support.|
|-t||Wrap the entire script in a transaction. Default.|
|-T||Remove the wrapper transaction. This is generally not a good idea as it can cause the table to appear completely empty to other clients during the data copying phase. If the entire process occurs inside a transaction, the update is atomic and other clients will have full access to all data in the table at all times.|
|-u||Issue a TRUNCATE TABLE statement to clear the contents of a table before copying data into it.|
TRUNCATE TABLE statement. Default.
The -c and -d arguments are incompatible with -u as its pointless to truncate a newly-created table. Specifying -c or -d will disable the TRUNCATE TABLE statement as though -U was given. Similarly, using the -u argument will disable the CREATE TABLE and DROP TABLE statements as if -C and -D were given.
When multiple incompatible interpretations of a type are available, such as the B type which can mean binary object in dBASE V or double-precision float in FoxPro, PgDBF currently uses the FoxPro interpretation.
Most XBase datatypes are supported, but some are not (yet). As of this writing, PgDBF can handle boolean, currency, date, double-precision float, float, general (although only outputs empty strings; its unclear how to resolve OLE objects at this time), integer, memo, numeric, timestamp, and varchar fields. If you need other datatypes, send a small sample database for testing.
Kirk Strauser <firstname.lastname@example.org>
|Version 0.6.2||PGDBF (1)||September 30 2012|