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

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 (view raw or flat)
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

pgsql-hackers by date

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

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