Re: COPY WITH CSV FORCE QUOTE *

Поиск
Список
Период
Сортировка
От Andrew Dunstan
Тема Re: COPY WITH CSV FORCE QUOTE *
Дата
Msg-id 4A5CB2E6.8040502@dunslane.net
обсуждение исходный текст
Ответ на Re: COPY WITH CSV FORCE QUOTE *  (Itagaki Takahiro <itagaki.takahiro@oss.ntt.co.jp>)
Ответы Re: COPY WITH CSV FORCE QUOTE * -- REVIEW  (Josh Berkus <josh@agliodbs.com>)
Re: COPY WITH CSV FORCE QUOTE *  (Josh Berkus <josh@agliodbs.com>)
Список pgsql-hackers

Itagaki Takahiro wrote:
>> Jaime Casanova <jcasanov@systemguards.com.ec> wrote:
>>
>>     
>>> i can find value for FORCE QUOTE * but what's
>>> the use case for FORCE NOT NULL?
>>>       
>
> Oh, sorry. I misread your mail.
> The patch adds * options "FORCE QUOTE" and "FORCE NOT NULL", too.
> Both of * mean all-columns for each options.
>
>   

I still don't understand the use case for FORCE NOT NULL *.

FORCE QUOTE * is relatively benign. In particular, it doesn't affect the 
null-preserving properties of our CSV implementation, since it still 
won't (or shouldn't) quote null values.

FORCE NOT NULL is in any case a fairly blunt instrument - it doesn't 
work for a column of any type that doesn't accept an empty string as 
valid input, such as numeric types.

I note that this patch was (I think) originally submitted without prior 
discussion. That's not following best practice.

cheers

andrew


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Heikki Linnakangas
Дата:
Сообщение: Re: [PATCH] "could not reattach to shared memory" on Windows
Следующее
От: Jeff Davis
Дата:
Сообщение: Re: WIP: Deferrable unique constraints