Re: COPY enhancements - Mailing list pgsql-hackers

From Robert Haas
Subject Re: COPY enhancements
Date
Msg-id 603c8f070909110834l4cc950baj108684d306f3ee0@mail.gmail.com
Whole thread Raw
In response to Re: COPY enhancements  (Pierre Frédéric Caillaud<lists@peufeu.com>)
Responses Re: COPY enhancements
List pgsql-hackers
2009/9/11 Pierre Frédéric Caillaud <lists@peufeu.com>:
>> I was thinking something like:
>>
>> COPY tablename [ ( column [, ...] ) ] FROM { 'filename' | STDIN }
>> [WITH] [option [, ...]]
>>
>> Where:
>>
>> option := ColId [Sconst] | FORCE NOT NULL (column [,...])
>>
>> I don't see any reasonable way to sandwhich the FORCE NOT NULL syntax
>> into a keyword/value notation.
>
>        Postgres has a hstore data type which seems well suited for passing
> key/value option pairs...
>        Why another syntax to remember, another parser to code, when almost
> everything is already there ?
>
>        Think about plpgsql code which generates some SQL COPY command
> string, then this is parsed and executed... wouldn't it be a lot simpler to
> just manipulate parameters in a hstore ?...

I doubt it very much.

...Robert


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: COPY enhancements
Next
From: Tom Lane
Date:
Subject: Re: Ragged CSV import