I made a mistake.
Postgres does put a NULL in the field (albiet I would still like to see
postgres/COPY change the NULL to TRUE if DEFAULT is set to true), it
appears pgAdmin III version 1.2.0 is the one displaying a boolean NULL
as FALSE (as opposed to NULL).
Sorry for not testing a little bit more before posting.
Thanks to all of you who responded.
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
pgsql-bugs by date
|Next:||From: Bruno Wolff III||Date: 2005-04-11 17:18:28|
|Subject: Re: BUG #1581: Problem with capitalised DB names...|
|Previous:||From: Tom Lane||Date: 2005-04-11 16:46:17|
|Subject: Re: BUG #1592: "with hold" cursor problem |