2008/10/13 Vladimir Dzhuvinov <vd@xxxxxxxxx>: > >>> So, is it true that as of Postgresql 8.3 there is no way to have a >>> pgpqsql function return multiple SELECTs? > >> it's true. > > Thank you for the definite answer, Pavel :) > > I came across a blog post of yours ( > http://okbob.blogspot.com/2007/11/stacked-recordset-multirecordset.html > ) as well as several list posts indicating that multiple result sets > might be in the working. Should I check the situation again when 8.4 is > released? > I have only very raw prototype, so I am sure, so this feature will not be in 8.4, and I am not sure about 8.5. It's nice feature, but I am not force to complete and clean code, and I am not able create patch. If you would do it, I am, with pleasure, send you source code, that allows multirecord sets. > >> You can use setof cursors instead. > > Cursors, unfortunately, look cumbersome in this situation and will break > the existing API (all transactions encapsulated within SPs, clients > allowed to do CALL only). Anyway, thanks everyone for the cursors tip :) > > > Vladimir > > -- > Vladimir Dzhuvinov * www.valan.net * PGP key ID AC9A5C6C > > -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
