Re: COPY enhancements

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Pierre Frédéric Caillaud <lists(at)peufeu(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Emmanuel Cecchet <manu(at)asterdata(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: COPY enhancements
Date: 2009-09-11 15:34:04
Message-ID: 603c8f070909110834l4cc950baj108684d306f3ee0@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2009/9/11 Pierre Frédéric Caillaud <lists(at)peufeu(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-09-11 15:35:58 Re: Ragged CSV import
Previous Message Robert Haas 2009-09-11 15:33:38 Re: COPY enhancements