Skip site navigation (1) Skip section navigation (2)

Re: pgsql: Changed TODO wording: < * Support procedures, which return no

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Changed TODO wording: < * Support procedures, which return no
Date: 2008-04-11 19:47:09
Message-ID: 16108.1207943229@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-committers
momjian(at)postgresql(dot)org (Bruce Momjian) writes:
> Log Message:
> -----------
> Changed TODO wording:

> < * Support procedures, which return no value
> > * Allow functions to control the transaction state

I can't imagine that we'd implement this by "allowing functions to
control the transaction state".  It would have to be some other sort
of object that is invoked in some entirely other way, perhaps
via a "PERFORM procedure_name..." kind of command.  Once you're inside
a SELECT you're not going to be committing anything.

			regards, tom lane

In response to

Responses

pgsql-committers by date

Next:From: Bruce MomjianDate: 2008-04-11 19:50:40
Subject: pgsql: Update wording: < * Allow functions to control the transaction
Previous:From: Bruce MomjianDate: 2008-04-11 19:36:08
Subject: pgsql: Changed TODO wording: < * Support procedures, which return no

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group