Re: SELECT INTO deprecation
От
Peter Eisentraut
Тема
Re: SELECT INTO deprecation
Дата
Msg-id
b2f854c2-f780-c739-064c-cb856e9e213f@enterprisedb.com
Ответ на
Re: SELECT INTO deprecation (Bruce Momjian)
Список
Дерево обсуждения
SELECT INTO deprecation Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: SELECT INTO deprecation Stephen Frost <sfrost@snowman.net>
Re: SELECT INTO deprecation Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: SELECT INTO deprecation Tom Lane <tgl@sss.pgh.pa.us>
Re: SELECT INTO deprecation Michael Paquier <michael@paquier.xyz>
Re: SELECT INTO deprecation Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: SELECT INTO deprecation Tom Lane <tgl@sss.pgh.pa.us>
Re: SELECT INTO deprecation Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: SELECT INTO deprecation Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: SELECT INTO deprecation Bruce Momjian <bruce@momjian.us>
Re: SELECT INTO deprecation Jan Wieck <jan@wi3ck.info>
Re: SELECT INTO deprecation Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: SELECT INTO deprecation Michael Paquier <michael@paquier.xyz>
Re: SELECT INTO deprecation Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: SELECT INTO deprecation David Fetter <david@fetter.org>
Re: SELECT INTO deprecation Thomas Kellerer <shammat@gmx.net>
Re: SELECT INTO deprecation Daniel Gustafsson <daniel@yesql.se>
Re: SELECT INTO deprecation Pavel Stehule <pavel.stehule@gmail.com>
On 2020-12-15 23:13, Bruce Momjian wrote: > Do we really want to carry around confusing syntax for compatibility? I > doubt we would ever add INTO now, even for compatibility. Right, we would very likely not add it now. But it doesn't seem to cause a lot of ongoing maintenance burden, so if there is a use case, it's not unreasonable to keep it around. I have no other motive here, I was just curious.
В списке pgsql-hackers по дате отправления
От: Fujii Masao
Дата: