Re: UPDATE using sub selects
От | NikhilS |
---|---|
Тема | Re: UPDATE using sub selects |
Дата | |
Msg-id | d3c4af540703160755y32f9cbc4we8f0b34aa98a141e@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: UPDATE using sub selects (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: UPDATE using sub selects
|
Список | pgsql-hackers |
Hi,
Regards,
Nikhils
--
EnterpriseDB http://www.enterprisedb.com
On 3/16/07, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Yeah, was looking at EXPR_SUBLINK and its single column use case and drove to the same conclusion that inventing a new sublink type would be better too. It is indeed becoming a "not so simple and narrow fix" as you had mentioned earlier in your first response :) NikhilS <nikkhils@gmail.com> writes:
> To allow both of the above to hold, I think the subselect will have to be
> treated like a EXPR_SUBLINK subquery. I was wondering if we have a similar
> mechanism for plain selects/subselects to check and restrict their output to
> a single row.
No. Offhand I think you'd either need to relax EXPR_SUBLINK to allow
multiple output columns, or invent a ROW_SUBLINK SubLinkType that is
just like EXPR_SUBLINK except for allowing multiple output columns.
The latter would probably be less likely to break other things...
Regards,
Nikhils
--
EnterpriseDB http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: