Re: proposal: table functions and plpgsql
От | Pavel Stehule |
---|---|
Тема | Re: proposal: table functions and plpgsql |
Дата | |
Msg-id | 162867790805211401ke8d9f62u5e287670fbb7174b@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: proposal: table functions and plpgsql (Hannu Krosing <hannu@krosing.net>) |
Список | pgsql-hackers |
2008/5/21 Hannu Krosing <hannu@krosing.net>: > On Wed, 2008-05-21 at 18:12 +0200, Pavel Stehule wrote: >> Hello > > ... > >> In my proposal I don't create any default variables. Result type is >> only virtual - I don't need write it to system directory. I thing it's >> better than using some specific predeclared type as RESULTTYPE OR >> RESULTSET. > > How is this different from using OUT params and RETURNS SETOF RECORD ? little - it's ANSI SQL compatible and I hope, it's less cryptic for beginers. > > hannu=# CREATE FUNCTION outsetof2py(n integer, OUT i integer, OUT j > integer) RETURNS SETOF record > AS $$ > for i in xrange(n): > yield {'i':i,'j':i*i} > $$ > LANGUAGE plpythonu; > CREATE FUNCTION > hannu=# select * from outsetof2py(3); > i | j > ---+--- > 0 | 0 > 1 | 1 > 2 | 4 > (3 rows) > > btw, this currently works for pl/python only in my local copy (still > testing for bugs), but similar declaration works fine for pl/pgsql > > -------------- My proposal is less relevant to external languages - there isn't problem with name collisions Pavel > Hannu > > >
В списке pgsql-hackers по дате отправления: