| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>, "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, Joost Kraaijeveld <J(dot)Kraaijeveld(at)Askesis(dot)nl>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL Top 10 Wishlist |
| Date: | 2006-01-19 01:22:15 |
| Message-ID: | 5945.1137633735@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
David Fetter <david(at)fetter(dot)org> writes:
> Although it might be nice to have different column orderings, say
> per-role, the SQL:2003 standard requires a single canonical ordering
> in the information schema. How would we handle both?
If you want some other column ordering, you make a view. The only thing
we're really lacking to make that a fully acceptable answer is
automatically-updatable views, which I believe someone is working on...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-01-19 01:25:34 | Re: No heap lookups on index |
| Previous Message | Jim C. Nasby | 2006-01-19 01:20:17 | Re: No heap lookups on index |