Re: COPY syntax improvement

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: COPY syntax improvement
Date: 2002-06-23 21:49:34
Message-ID: Pine.LNX.4.44.0206202126310.1267-100000@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian writes:

> I thought there were complaints that the old COPY syntax just had too
> many features stuffed in too many unusual places,

Haven't ever seen one. This command has no precedent in other products,
only years of going virtually unchanged in PostgreSQL. Changing it now
and allowing countless permutations of the key words is going to be
confusing, IMHO.

> e.g. delimiter after
> filename,

COPY is the only command to use a delimiter, so this can hardly be
qualified as an "unusual" place.

> oids after tablename,

That's because the OIDs are in said table.

> binary after COPY,

Which is consistent with DECLARE BINARY CURSOR.

> NULL after delimiter.

OK, that order should perhaps be more flexible.

--
Peter Eisentraut peter_e(at)gmx(dot)net

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2002-06-23 21:50:49 Re: SQL99, CREATE CAST, and initdb
Previous Message Bruce Momjian 2002-06-23 21:16:09 Re: A fairly obvious optimization?