Re: COPY incorrectly uses null instead of an empty string in last field - Mailing list pgsql-hackers

From Zeugswetter Andreas SB SD
Subject Re: COPY incorrectly uses null instead of an empty string in last field
Date
Msg-id 46C15C39FEB2C44BA555E356FBCD6FA41EB52B@m0114.s-mxs.net
Whole thread Raw
In response to COPY incorrectly uses null instead of an empty string in last field  (Oliver Elphick <olly@lfix.co.uk>)
List pgsql-hackers
> >> One of the things we've agreed to do in 7.3 is change COPY IN to remove
> >> that assumption --- a line with too few fields (too few tabs) will draw
> >> an error report instead of silently doing what's likely the wrong thing.
>
> > But there will be new syntax for COPY, that allows missing trailing columns.
> > I hope.
>
> Why?

Well, good question. For one for backwards compatibility.
I guess I would prefer COPY syntax that allows you to specify columns
as has been previously discussed. Having that, that would be sufficient
and safer than only a switch.

COPY 'afile' to atab (a1, a3, a5, a2)

Andreas


pgsql-hackers by date:

Previous
From: mlw
Date:
Subject: Re: Oracle vs PostgreSQL in real life
Next
From: Hannu Krosing
Date:
Subject: Re: Oracle vs PostgreSQL in real life