Re: [BUGS] BUG #1643: dbf2pg broken + quick fix

2005-05-06 Thread Boris van Schooten
eporting that helped me find this bug, I suppose. Kind regards, Boris van Schooten On Thu, 5 May 2005, Tom Lane wrote: > Boris van Schooten <[EMAIL PROTECTED]> writes: > > Looks good to me. I'd prefer to have a warning message (if (verbose) > > fprintf stderr) for each o

Re: [BUGS] BUG #1643: dbf2pg broken + quick fix

2005-05-05 Thread Boris van Schooten
Looks good to me. I'd prefer to have a warning message (if (verbose) fprintf stderr) for each of the exceptional conditions though. I'm even so paranoid I prefer to have the verbose switch on by default. Kinds regards, Boris van Schooten On Wed, 4 May 2005, Tom Lane wrote: &

Re: [BUGS] BUG #1643: dbf2pg broken + quick fix

2005-05-04 Thread Boris van Schooten
he bug report form on the postgres site. I got mails which suggest that the message bounced. Later I sent a mail to Bruce Momjian. I never knew if you replied to the bug report or to the mail to Bruce. Do you know what happened here? Do bug reports get bounced? Kind regards, Boris van Schooten On

Re: [BUGS] BUG #1643: dbf2pg broken + quick fix

2005-05-04 Thread Boris van Schooten
hough. I am not a dbase expert, I just run into dbfs often when trying to enter gis data into postgis. Kind regards, Boris van Schooten On Tue, 3 May 2005, Tom Lane wrote: > "Boris van Schooten" <[EMAIL PROTECTED]> writes: > > As it turns out, the integer checkin

[BUGS] BUG #1643: dbf2pg broken + quick fix

2005-05-03 Thread Boris van Schooten
The following bug has been logged online: Bug reference: 1643 Logged by: Boris van Schooten Email address: [EMAIL PROTECTED] PostgreSQL version: 7.4.5, 8.0.2 Operating system: FreeBSD Description:dbf2pg broken + quick fix Details: As several people on the mailing