Re: Review: UNNEST (and other functions) WITH ORDINALITY
От | Robert Haas |
---|---|
Тема | Re: Review: UNNEST (and other functions) WITH ORDINALITY |
Дата | |
Msg-id | CA+TgmobmHVmHuw_nT3LV7ToKzxSGnW+=W=Xz_H7Xj5r6qgW+2A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Review: UNNEST (and other functions) WITH ORDINALITY (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-hackers |
On Wed, Jul 24, 2013 at 1:36 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Robert Haas <robertmhaas@gmail.com> writes: >> On Tue, Jul 23, 2013 at 9:38 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: >>> If it weren't that we've been speculating for years about deprecating >>> SRFs-in-tlists once we had LATERAL, I would personally consider this >>> patch DOA in this form. > >> I guess I'd sort of assumed that the plan was to continue accepting >> SRFs in tlists but rewrite them as lateral joins, rather than getting >> rid of them altogether. > > That seems to me to be unlikely to happen, because it would be > impossible to preserve the current (admittedly bad) semantics. > If we're going to change the behavior at all we might as well just > drop the feature, IMO. Maybe. I'd be kind of sad to lose some of the simple cases that work now, like SELECT srf(), in favor of having to write SELECT * FROM srf(). I'd probably get over it, but I'm sure a lot of people would be mildly annoyed at having to change their working application code. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: