Re: COPY enhancements

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Emmanuel Cecchet <manu(at)asterdata(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(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 14:18:51
Message-ID: 19938.1252678731@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Emmanuel Cecchet <manu(at)asterdata(dot)com> writes:
> The new syntax could look like:

> COPY /tablename/ [ ( /column/ [, ...] ) ]
> FROM { '/filename/' | STDIN }
> [ [, BINARY ]
> [, OIDS ]
> [, DELIMITER [ AS ] '/delimiter/' ]
> [, NULL [ AS ] '/null string/' ]
> [, CSV [ HEADER ]
> [ QUOTE [ AS ] '/quote/' ]
> [ ESCAPE [ AS ] '/escape/' ]
> [ FORCE NOT NULL (/column/ [, ...]) ]
> [, ERRORS { SKIP |
> LOG INTO { tablename | 'filename' }
> [ LABEL label_name ]
> [ KEY key_name ]
> [ MAX ERRORS /count/ ] } ]

> Is this what you had in mind?

No. because that doesn't do a darn thing to make the option set less
hard-wired into the syntax. I was thinking of a strict keyword/value
format with non-wired-in keywords ... and only *one* keyword per value.
See EXPLAIN.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2009-09-11 14:24:55 Re: RfD: more powerful "any" types
Previous Message Tom Lane 2009-09-11 14:08:32 Re: Why does LOG have higher priority than ERROR and WARNING?