Re: RETURNING clause: how to specifiy column indexes?
От
Kris Jurka
Тема
Re: RETURNING clause: how to specifiy column indexes?
Дата
Msg-id
Pine.BSO.4.64.0712120138360.1768@leary.csoft.net
Ответ на
Список
Дерево обсуждения
Re: RETURNING clause: how to specifiy column indexes? Tom Lane <tgl@sss.pgh.pa.us>
Re: RETURNING clause: how to specifiy column indexes? Kris Jurka <books@ejurka.com>
Re: RETURNING clause: how to specifiy column indexes? Tom Lane <tgl@sss.pgh.pa.us>
Re: RETURNING clause: how to specifiy column indexes? Ken Johanson <pg-user@kensystem.com>
Re: RETURNING clause: how to specifiy column indexes? Ken Johanson <pg-user@kensystem.com>
Re: RETURNING clause: how to specifiy column indexes? Kris Jurka <books@ejurka.com>
Re: RETURNING clause: how to specifiy column indexes? Ken Johanson <pg-user@kensystem.com>
Re: RETURNING clause: how to specifiy column indexes? Ken Johanson <pg-user@kensystem.com>
Re: RETURNING clause: how to specifiy column indexes? Kris Jurka <books@ejurka.com>
Re: RETURNING clause: how to specifiy column indexes? Ken Johanson <pg-user@kensystem.com>
On Wed, 12 Dec 2007, Tom Lane wrote: > Every few weeks we get a complaint from someone who thinks that it > should be easy to rearrange the logical order of table columns. > If that comes to pass, it would be a seriously bad idea to have > encouraged applications to rely on table column numbers. I think the expectation is that: CREATE TABLE t(a int, b int); INSERT INTO t(b,a) VALUES (1,2) RETURNING *; will return 1,2 instead of 2,1 as it does now. In this case the op is not expecting that the (potentially reorganized) table order is driving the results, but the order that they've actually specified the columns in creates the result. Kris Jurka
В списке pgsql-general по дате отправления