Re: functions returning records
От | Alex Pilosov |
---|---|
Тема | Re: functions returning records |
Дата | |
Msg-id | Pine.BSO.4.10.10106272122030.7004-100000@spider.pilosoft.com обсуждение исходный текст |
Ответ на | Re: functions returning records (Jan Wieck <JanWieck@Yahoo.com>) |
Ответы |
Re: functions returning records
Re: functions returning records |
Список | pgsql-hackers |
On Wed, 27 Jun 2001, Jan Wieck wrote: > Alex Pilosov wrote: > > On Thu, 28 Jun 2001, Hannu Krosing wrote: > > > > > > How hard would it be to turn this around and implement RETURN AND > > > CONTINUE > > > for at least PL/PGSQL, and possibly C/Perl/Python ... ? > > Cannot talk about plpgsql, but for c this would be probably implemented > > with setjmp and with perl with goto. Probably not very complex. > > Don't think so. When the function returns, the call stack > get's destroyed. Jumping back to there - er - the core dump > is not even useful any more. Or did I miss something? Well, it shouldn't return, but instead save the location and longjmp to SPI_RESUME_jmp location. On a next call, instead of a function call, it should longjmp back to saved location. I have to admit its more complex than I originally thought, but probably doable. -alex
В списке pgsql-hackers по дате отправления: