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 m
On Tue, Apr 05, 2005 at 21:11:12 +0100,
Eric McGough <[EMAIL PROTECTED]> wrote:
>
> COPY my_table FROM STDIN WITH DELIMITER AS '|';
> \N|\N|\N
> \.
COPY doesn't provide a way to use default values for just some rows.
You can get the default for a column by leaving it out of an explicit
column l
"Eric McGough" <[EMAIL PROTECTED]> writes:
> -- This table and COPY command should result in all
> -- three columns defaulting to TRUE based on NULL
> -- inputs, but they all result in FALSE. Not sure why?
No, it's filling with NULL, which is what the input specifies.
rega
The following bug has been logged online:
Bug reference: 1582
Logged by: Eric McGough
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating system: Solaris 8
Description:boolean DEFAULT TRUE results in FALSE for NULL values
Details:
-- This table and
