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>,"Oliver Elphick" <olly(at)lfix(dot)co(dot)uk>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: COPY incorrectly uses null instead of an empty string in last field
Date: 2002-02-27 09:19:40
Message-ID: 46C15C39FEB2C44BA555E356FBCD6FA41EB527@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.

Andreas

Responses

pgsql-hackers by date

Next:From: Jean-Paul ARGUDODate: 2002-02-27 09:48:15
Subject: Yet again on indices...
Previous:From: Karel ZakDate: 2002-02-27 08:52:51
Subject: Re: timestamp_part() bug?

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