| From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
|---|---|
| To: | Antti Haapala <antti(dot)haapala(at)iki(dot)fi> |
| Cc: | 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: | Re: Changing Column Order (Was Re: MySQL vs PostgreSQL.) |
| Date: | 2002-10-12 15:45:13 |
| Message-ID: | 20021012154513.GA12337@wolff.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers pgsql-jdbc |
On Sat, Oct 12, 2002 at 12:43:37 +0300,
Antti Haapala <antti(dot)haapala(at)iki(dot)fi> wrote:
>
> > I cannot think of any reason why changing column order should be
> > implemented in Postgres. Seems like a waste of time/more code bloat for
> > something which is strictly asthetic.
>
> 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Smarzewski | 2002-10-12 16:31:50 | certified installer/administrator |
| Previous Message | Bruce Momjian | 2002-10-12 14:37:32 | Re: MySQL vs PostgreSQL. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Darko Prenosil | 2002-10-12 18:58:53 | Re: [HACKERS] MySQL vs PostgreSQL. |
| Previous Message | Bruce Momjian | 2002-10-12 14:45:32 | Re: Script to compute random page cost |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Darko Prenosil | 2002-10-12 18:58:53 | Re: [HACKERS] MySQL vs PostgreSQL. |
| Previous Message | Dave Cramer | 2002-10-12 14:46:07 | cursor based result sets not updateable |