From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: COPY syntax improvement |
Date: | 2002-06-23 21:51:02 |
Message-ID: | 200206232151.g5NLp2f20161@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Well, good points. I know there were some people who wanted a clearer
syntax, so I supplied it. Seems you don't. I would like to hear from
someone else who doesn't like the improved syntax before I consider
changing things back.
---------------------------------------------------------------------------
Peter Eisentraut wrote:
> 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
>
>
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2002-06-23 21:51:10 | Re: SQL99, CREATE CAST, and initdb |
Previous Message | Peter Eisentraut | 2002-06-23 21:50:49 | Re: SQL99, CREATE CAST, and initdb |