Re: BUG #1643: dbf2pg broken + quick fix

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Boris van Schooten <schooten(at)cs(dot)utwente(dot)nl>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1643: dbf2pg broken + quick fix
Date: 2005-05-05 13:33:56
Message-ID: 22660.1115300036@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Boris van Schooten <schooten(at)cs(dot)utwente(dot)nl> writes:
> 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.

Don't really see the need for it. What we are doing here is trusting to
the backend to error-check the input, rather than making a half-baked
attempt to do error checking in dbf2pg.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2005-05-05 14:15:31 Re: BUG #1649: Date calculation year off-by-one error
Previous Message Boris van Schooten 2005-05-05 09:34:06 Re: BUG #1643: dbf2pg broken + quick fix