> >> 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.
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)
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2002-02-27 16:21:30|
|Subject: Re: COPY incorrectly uses null instead of an empty string in last field |
|Previous:||From: mlw||Date: 2002-02-27 16:07:19|
|Subject: Re: Oracle vs PostgreSQL in real life|