\copy needs work (was Re: Changing Column Order)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruno Wolff III <bruno(at)wolff(dot)to>
Cc: Antti Haapala <antti(dot)haapala(at)iki(dot)fi>, Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>, Hannu Krosing <hannu(at)tm(dot)ee>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: \copy needs work (was Re: Changing Column Order)
Date: 2002-10-12 20:36:44
Message-ID: 14051.1034455004@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers pgsql-jdbc

Bruno Wolff III <bruno(at)wolff(dot)to> writes:
> On Sat, Oct 12, 2002 at 12:43:37 +0300,
> Antti Haapala <antti(dot)haapala(at)iki(dot)fi> wrote:
>> What about copy? AFAIK, copy doesn't allow column names being specified,
>> so it's not purely aesthetic...

> The SQL COPY command does (at least in 7.3). The \copy psql command
> doesn't seem to allow this though.

That's an oversight; \copy should have been fixed for 7.3.

Do we want to look at this as a bug (okay to fix for 7.3) or a new
feature (wait for 7.4)?

I see something that I think is a must-fix omission in the same code:
it should allow a schema-qualified table name. So I'm inclined to fix
both problems now.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2002-10-13 00:30:48 Re: question about executing JOINs
Previous Message Robert Fitzpatrick 2002-10-12 19:28:03 Re: Removing {"="} privledges

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-10-12 20:57:42 \copy and identifier quoting
Previous Message Tom Lane 2002-10-12 20:26:47 Re: Triggers and Schema's.

Browse pgsql-jdbc by date

  From Date Subject
Next Message Mike Coleman 2002-10-12 21:44:53 Re: 7.3 top-of-tree compilation error on OSX
Previous Message Nic Ferrier 2002-10-12 19:50:27 problem with the build file?