Re: returning multiple result sets from a stored procedure
От | Kevin Grittner |
---|---|
Тема | Re: returning multiple result sets from a stored procedure |
Дата | |
Msg-id | 4C88FC8602000025000354A1@gw.wicourts.gov обсуждение исходный текст |
Ответ на | Re: returning multiple result sets from a stored procedure (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: returning multiple result sets from a stored procedure
Re: returning multiple result sets from a stored procedure |
Список | pgsql-hackers |
Tom Lane <tgl@sss.pgh.pa.us> wrote: > to my mind the main thing that would justify inventing a separate > PROCEDURE facility is if procedures were to execute outside the > transaction system, so that they could start and stop transactions > for themselves. That is the biggest distinction in my mind, too. Supporting multiple result sets just as if the queries were run as independent client-side statements would also be very important. I have seen implementations which support, for a single stored procedure, OUT parameters, a RETURN value, and multiple result sets -- all at the same time, as separate things. I haven't reviewed stored procedures in the SQL standard since an early draft proposal years ago, so I don't know what the current state of that is, but if PostgreSQL approaches this, it'd be nice to implement as many of the above as are not in conflict with requirements of the standard. -Kevin
В списке pgsql-hackers по дате отправления: