RE: FW: Dbf to Pg converter - Mailing list pgsql-general

From Joseph
Subject RE: FW: Dbf to Pg converter
Date
Msg-id CLEJKCMNOMBPKNIAIODGGEBMCAAA.lters@mrtc.com
Whole thread Raw
In response to Re: FW: Dbf to Pg converter  (martin.chantler@convergys.com)
Responses RE: FW: Dbf to Pg converter
List pgsql-general
I am interested.

I tryed to use dbfdump 1.6.0 but it crashes on my large databases. Segment
fail.


Joseph Showalter

-----Original Message-----
From: pgsql-general-owner@postgresql.org
[mailto:pgsql-general-owner@postgresql.org]On Behalf Of
martin.chantler@convergys.com
Sent: Tuesday, February 20, 2001 4:47 AM
To: Len Morgan
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] FW: Dbf to Pg converter



FYI I have hacked around with this to make a another sort of import program
for DBF's.



First there's a Foxpro export program that exports all databases to
      individual text files containing SQL

This renames invalid field/table names and handles embedded quotes and
      CR/LF's in text, that sort of thing.



On the Linux box, there is a text file of all the text files to be imported
      (one file per table)

A C program reads this and the SQL inside performed (e.g. create table and
      lots of inserts)

If a file imports it is removed from the main file, so it can be re-run in
      case of failure of

any one file. This makes it much easier to handle errors when you have lots
      of tables/data



I used it to import all data from a large Foxpro database but would also
      work for DBase/Clipper

Memo's are not properly supported yet...



Its very fast, unlike ODBC which is why I did it in the first place!



I anyone is interested I will send it to you,

MC.



--

NOTICE:  The information contained in this electronic mail transmission is
intended by Convergys Corporation for the use of the named individual or
entity to which it is directed and may contain information that is
privileged or otherwise confidential.  If you have received this electronic
mail transmission in error, please delete it from your system without
copying or forwarding it, and notify the sender of the error by reply email
or by telephone (collect), so that the sender's address records can be
corrected.


pgsql-general by date:

Previous
From: Peep Krusberg
Date:
Subject: win2000: problems starting postmaster
Next
From: Thierry Besancon
Date:
Subject: binding postmaster to *one* virtual IP address