Postgres Pro
Downloads
Home   >   mailing lists

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

From Tom Lane
Subject Re: COPY incorrectly uses null instead of an empty string in last field
Date
Msg-id 22060.1014821657@sss.pgh.pa.us
Whole thread Raw
In response to Re: COPY incorrectly uses null instead of an empty string in last field  ("Zeugswetter Andreas SB SD" <ZeugswetterA@spardat.at>)
List pgsql-hackers
Tree view 
"Zeugswetter Andreas SB SD" <ZeugswetterA@spardat.at> writes:
>> 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?
        regards, tom lane

pgsql-hackers by date:

Previous
From: F Harvell
Date:
Subject: Re: eWeek Poll: Which database is most critical to
Next
From: Jean-Paul ARGUDO
Date:
Subject: Re: Yet again on indices...