Re: Is it possible to return custom type as proper ROW?
| От | Merlin Moncure |
|---|---|
| Тема | Re: Is it possible to return custom type as proper ROW? |
| Дата | |
| Msg-id | b42b73150610111306r6ef83d77g727d1b0d05e89465@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Is it possible to return custom type as proper ROW? ("Uwe C. Schroeder" <uwe@oss4u.com>) |
| Ответы |
Re: Is it possible to return custom type as proper ROW?
|
| Список | pgsql-general |
On 10/11/06, Uwe C. Schroeder <uwe@oss4u.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
В списке pgsql-general по дате отправления: