Re: Patch: FORCE_NULL option for copy COPY in CSV mode - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Patch: FORCE_NULL option for copy COPY in CSV mode
Date
Msg-id 52559988.5000606@dunslane.net
Whole thread Raw
In response to Re: Patch: FORCE_NULL option for copy COPY in CSV mode  (David Fetter <david@fetter.org>)
List pgsql-hackers
On 10/09/2013 01:25 PM, David Fetter wrote:
>
> Idea:
>
> NULL FOR (foo,bar,baz,blurf) AS '""', NULL FOR (quux,fleeg) AS ...,
>
>


What's the point of this? How is this superior to what is currently 
proposed? Having arbitrary NULL markers for different fields will 
significantly increase code complexity for a case I have a hard time 
believing exists to any significant degree in the real world. The ONLY 
case I know of outside some fervid imaginations where we need to 
distinguish between  different NULL treatment is quoted vs unquoted, 
which this patch rounds out. Catering for anything else seems quite 
unnecessary.

What is more, I think it's actually far more obscure than what is 
proposed, which fits in nicely with our existing pattern of options.

cheers

andrew



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Auto-tuning work_mem and maintenance_work_mem
Next
From: Jim Nasby
Date:
Subject: Re: Triggers on foreign tables