Re: COPY incorrectly uses null instead of an empty string in last field

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at>
Cc: "Oliver Elphick" <olly(at)lfix(dot)co(dot)uk>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: COPY incorrectly uses null instead of an empty string in last field
Date: 2002-02-27 14:54:17
Message-ID: 22060.1014821657@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jean-Paul ARGUDO 2002-02-27 14:59:00 Re: Yet again on indices...
Previous Message F Harvell 2002-02-27 14:51:03 Re: eWeek Poll: Which database is most critical to