| From: | "Merlin Moncure" <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | "Uwe C(dot) Schroeder" <uwe(at)oss4u(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org, "A(dot) Kretschmer" <andreas(dot)kretschmer(at)schollglas(dot)com> |
| Subject: | Re: Is it possible to return custom type as proper ROW? |
| Date: | 2006-10-11 20:06:42 |
| Message-ID: | b42b73150610111306r6ef83d77g727d1b0d05e89465@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 10/11/06, Uwe C. Schroeder <uwe(at)oss4u(dot)com> wrote:
> Well, "SELECT *" is only evil if your application relies on a specific column
> order to function. The moment you change the table layout and you're using
> "select *" your application will cease functioning.
> My app uses tons of select *, but then I wrote an object mapper that queries
> the information schema at startup - so it's aware of table changes and
> adjusts accordingly.
+1
assumed column ordering is the real enemy. Here is another place
where select * is imo better style than non select *:
select q.*, bar from
(
select a, b,c from foo
) q;
what I really wish sql had was the ability to select all but a
particular column :)
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-10-11 20:29:26 | Re: invalid data in PID file |
| Previous Message | Jim C. Nasby | 2006-10-11 20:06:41 | Re: Clarification needed |