Re: \copy needs work (was Re: Changing Column Order)
Bruce Momjian <pgman@candle.pha.pa.us>
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Bruno Wolff III <bruno@wolff.to>, Antti Haapala <antti.haapala@iki.fi>, Gavin Sherry <swm@linuxworld.com.au>, Hannu Krosing <hannu@tm.ee>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2002-10-14T03:45:36Z
Lists: pgsql-hackers, pgsql-general
Tom Lane wrote: > Bruno Wolff III <bruno@wolff.to> writes: > > On Sat, Oct 12, 2002 at 12:43:37 +0300, > > Antti Haapala <antti.haapala@iki.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. I don't think we can say \copy missing columns is a bug; we never had it in previous release. Seems like a missing feature. The COPY schema names seems valid. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073