| From: | Antti Haapala <antti(dot)haapala(at)iki(dot)fi> |
|---|---|
| To: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> |
| Cc: | 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 09:43:37 |
| Message-ID: | Pine.GSO.4.44.0210121234220.23107-100000@paju.oulu.fi |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers pgsql-jdbc |
> 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...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2002-10-12 09:54:20 | Re: Changing Column Order (Was Re: MySQL vs PostgreSQL.) |
| Previous Message | Hannu Krosing | 2002-10-12 08:57:32 | Re: MySQL vs PostgreSQL. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2002-10-12 09:54:20 | Re: Changing Column Order (Was Re: MySQL vs PostgreSQL.) |
| Previous Message | Hannu Krosing | 2002-10-12 08:57:32 | Re: MySQL vs PostgreSQL. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2002-10-12 09:54:20 | Re: Changing Column Order (Was Re: MySQL vs PostgreSQL.) |
| Previous Message | Hannu Krosing | 2002-10-12 08:57:32 | Re: MySQL vs PostgreSQL. |