Skip site navigation (1) Skip section navigation (2)

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

From: "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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:13:53
Message-ID: 46C15C39FEB2C44BA555E356FBCD6FA41EB52B@m0114.s-mxs.net (view raw or flat)
Thread:
Lists: pgsql-hackers
> >> 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

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2002-02-27 16:21:30
Subject: Re: COPY incorrectly uses null instead of an empty string in last field
Previous:From: mlwDate: 2002-02-27 16:07:19
Subject: Re: Oracle vs PostgreSQL in real life

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group