Postgres Pro
Downloads
Home   >   mailing lists

Re: COPY incorrectly uses null instead of an empty string in last field - Mailing list pgsql-hackers

From Zeugswetter Andreas SB SD
Subject Re: COPY incorrectly uses null instead of an empty string in last field
Date
Msg-id 46C15C39FEB2C44BA555E356FBCD6FA41EB527@m0114.s-mxs.net
Whole thread Raw
In response to COPY incorrectly uses null instead of an empty string in last field  (Oliver Elphick <olly@lfix.co.uk>)
Responses Re: COPY incorrectly uses null instead of an empty string in last field  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
> 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

pgsql-hackers by date:

Previous
From: Karel Zak
Date:
Subject: Re: timestamp_part() bug?
Next
From: Jean-Paul ARGUDO
Date:
Subject: Yet again on indices...