Re: Review: Patch FORCE_NULL option for copy COPY in CSV mode

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Ian Lawrence Barwick <barwick(at)gmail(dot)com>, Payal Singh <payal(at)omniti(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Review: Patch FORCE_NULL option for copy COPY in CSV mode
Date: 2014-03-05 14:11:41
Message-ID: CAB7nPqRquusDi291GdjTjQq2Zv8aP8JGFP6NWM_84O7eU5bznA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

After testing this feature, I noticed that FORCE_NULL and
FORCE_NOT_NULL can both be specified with COPY on the same column.
This does not seem correct. The attached patch adds some more error
handling, and a regression test case for that.
Regards,
--
Michael

Attachment Content-Type Size
20140305_copy_force_error.patch text/plain 2.3 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2014-03-05 14:27:56 Re: Review: Patch FORCE_NULL option for copy COPY in CSV mode
Previous Message Heikki Linnakangas 2014-03-05 12:51:36 Re: Hot standby doesn't come up on some situation.