
> >> 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

Wed, 27 Feb 2002 17:13:53 +0100
"Zeugswetter Andreas SB SD" <ZeugswetterA@spardat.at>
Re: COPY incorrectly uses null instead of an empty string in last
	field
"Zeugswetter Andreas SB SD" <ZeugswetterA@spardat.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

Wed, 27 Feb 2002 11:21:30 -0500
Tom Lane <tgl@sss.pgh.pa.us>
Re: COPY incorrectly uses null instead of an empty string in last
	field