Re: CALL versus procedures with output-only arguments
От
Laurenz Albe
Тема
Re: CALL versus procedures with output-only arguments
Дата
Msg-id
efe55e8d2d83c3761e46789fa86cdc4b013a7ba6.camel@cybertec.at
Ответ на
Список
Дерево обсуждения
CALL versus procedures with output-only arguments Tom Lane <tgl@sss.pgh.pa.us>
Re: CALL versus procedures with output-only arguments Tom Lane <tgl@sss.pgh.pa.us>
Re: CALL versus procedures with output-only arguments Tom Lane <tgl@sss.pgh.pa.us>
Re: CALL versus procedures with output-only arguments Andrew Dunstan <andrew@dunslane.net>
Re: CALL versus procedures with output-only arguments Tom Lane <tgl@sss.pgh.pa.us>
Re: CALL versus procedures with output-only arguments Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: CALL versus procedures with output-only arguments Tom Lane <tgl@sss.pgh.pa.us>
Re: CALL versus procedures with output-only arguments Tom Lane <tgl@sss.pgh.pa.us>
Re: CALL versus procedures with output-only arguments Robert Haas <robertmhaas@gmail.com>
Re: CALL versus procedures with output-only arguments Tom Lane <tgl@sss.pgh.pa.us>
Re: CALL versus procedures with output-only arguments Robert Haas <robertmhaas@gmail.com>
Re: CALL versus procedures with output-only arguments Tom Lane <tgl@sss.pgh.pa.us>
Re: CALL versus procedures with output-only arguments Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: CALL versus procedures with output-only arguments Tom Lane <tgl@sss.pgh.pa.us>
Re: CALL versus procedures with output-only arguments Tom Lane <tgl@sss.pgh.pa.us>
Re: CALL versus procedures with output-only arguments Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: CALL versus procedures with output-only arguments Tom Lane <tgl@sss.pgh.pa.us>
Re: CALL versus procedures with output-only arguments Tom Lane <tgl@sss.pgh.pa.us>
Re: CALL versus procedures with output-only arguments Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: CALL versus procedures with output-only arguments Tom Lane <tgl@sss.pgh.pa.us>
Re: CALL versus procedures with output-only arguments Tom Lane <tgl@sss.pgh.pa.us>
Re: CALL versus procedures with output-only arguments Tom Lane <tgl@sss.pgh.pa.us>
Re: CALL versus procedures with output-only arguments Andrew Dunstan <andrew@dunslane.net>
Re: CALL versus procedures with output-only arguments Tom Lane <tgl@sss.pgh.pa.us>
Re: CALL versus procedures with output-only arguments Andrew Dunstan <andrew@dunslane.net>
Re: CALL versus procedures with output-only arguments Tom Lane <tgl@sss.pgh.pa.us>
Re: CALL versus procedures with output-only arguments Andrew Dunstan <andrew@dunslane.net>
Re: CALL versus procedures with output-only arguments Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: CALL versus procedures with output-only arguments Tom Lane <tgl@sss.pgh.pa.us>
Re: CALL versus procedures with output-only arguments Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: CALL versus procedures with output-only arguments Tom Lane <tgl@sss.pgh.pa.us>
Re: CALL versus procedures with output-only arguments Tom Lane <tgl@sss.pgh.pa.us>
Re: CALL versus procedures with output-only arguments Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: CALL versus procedures with output-only arguments Tom Lane <tgl@sss.pgh.pa.us>
Re: CALL versus procedures with output-only arguments Tom Lane <tgl@sss.pgh.pa.us>
Re: CALL versus procedures with output-only arguments Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: CALL versus procedures with output-only arguments Tom Lane <tgl@sss.pgh.pa.us>
Re: CALL versus procedures with output-only arguments Tom Lane <tgl@sss.pgh.pa.us>
Re: CALL versus procedures with output-only arguments Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: CALL versus procedures with output-only arguments Andrew Dunstan <andrew@dunslane.net>
Re: CALL versus procedures with output-only arguments Laurenz Albe <laurenz.albe@cybertec.at>
Re: CALL versus procedures with output-only arguments "David G. Johnston" <david.g.johnston@gmail.com>
Re: CALL versus procedures with output-only arguments Tom Lane <tgl@sss.pgh.pa.us>
Re: CALL versus procedures with output-only arguments Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: CALL versus procedures with output-only arguments Tom Lane <tgl@sss.pgh.pa.us>
Re: CALL versus procedures with output-only arguments Pavel Stehule <pavel.stehule@gmail.com>
On Mon, 2021-05-31 at 15:55 -0400, Tom Lane wrote: > > If I have two procedures > > p1(IN int, IN int, OUT int, OUT int) > > p1(OUT int, OUT int) > > then a DROP, or ALTER, or GRANT, etc. on p1(int, int) should operate on > > the second one in a spec-compliant implementation, but you propose to > > have it operate on the first one. That kind of discrepancy would be > > really bad to have. > > We already have that situation for functions. I think having procedures > work differently from functions is much worse than your complaint here; > and I do not see why being spec-compliant for one case when we are not > for the other is a good situation to be in. +1 Yours, Laurenz Albe
В списке pgsql-hackers по дате отправления
От: Michael Paquier
Дата:
От: Michael Paquier
Дата: