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 16:21:30
Message-ID: 25800.1014826890@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:
> But there will be new syntax for COPY, that allows missing trailing columns.
> I hope.
>>
>> Why?

> Well, good question. For one for backwards compatibility.

It's an undocumented feature. How many people are likely to be using it?

> I guess I would prefer COPY syntax that allows you to specify columns
> as has been previously discussed.

Yes, that's on the to-do list as well. But no matter what the expected
set of columns is, COPY ought to complain if a line is missing some
fields.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message mlw 2002-02-27 16:48:34 Re: single task postgresql
Previous Message Zeugswetter Andreas SB SD 2002-02-27 16:13:53 Re: COPY incorrectly uses null instead of an empty string in last field