| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Ian Lawrence Barwick <barwick(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Patch: FORCE_NULL option for copy COPY in CSV mode |
| Date: | 2013-10-10 00:39:03 |
| Message-ID: | CA+TgmoY1-K1h5YT8S5nP=m27RxcZ6AD1bXgRQBcn33HJRrmA6w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Oct 9, 2013 at 5:43 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> On 10/09/2013 03:25 PM, Robert Haas wrote:
>> Therefore, a user who wants the opposite of the default behavior -
>> namely, unquoted empty strings as empty strings and quoted empty
>> strings as nulls - should specify both FORCE NULL and FORCE NOT NULL.
>
> Is there a real world example of this case? How common is it? And how come I
> haven't heard of it in the nine or so years since we've been supporting CSV
> import?
I doubt there is any real world use case. My point is just that FORCE
NULL and FORCE NOT NULL are not opposites, and that will probably
confuse some people.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2013-10-10 00:54:54 | Re: Patch: FORCE_NULL option for copy COPY in CSV mode |
| Previous Message | Robert Haas | 2013-10-10 00:37:17 | Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE |