Re: DO ... RETURNING
От | Pavel Stehule |
---|---|
Тема | Re: DO ... RETURNING |
Дата | |
Msg-id | CAFj8pRCrB0_EYdefaVx=9zRh=L=jxwn89xMdhDXTEaDP-x6y7A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: DO ... RETURNING (Stephen Frost <sfrost@snowman.net>) |
Ответы |
Re: DO ... RETURNING
Re: DO ... RETURNING |
Список | pgsql-hackers |
2013/6/11 Stephen Frost <sfrost@snowman.net>: > * Merlin Moncure (mmoncure@gmail.com) wrote: >> I agree with all your comments pretty much down the line. Need top >> level CALL that supports parameterization and multiple sets that >> utilizes background worker (we have example spi worker that gives some >> hints about how pl/pgsql could be made to work). Because it's top >> level (can't even be inlined to CTE), we can access behaviors that are >> not possible in current pl/pgsql, for example setting transaction >> isolation in advance of snapshot and changing database connection >> mid-procedure. > > And this still has next-to-nothing to do with the specific proposal that > was put forward. > > I'd like actual procedures too, but it's a completely different and > distinct thing from making DO blocks able to return something. I think so it is related - we talk about future form of DO statement - or about future form of server side scripting. But it is not important in this moment Pavel > > Thanks, > > Stephen
В списке pgsql-hackers по дате отправления: