Tom Lane wrote:
> [EMAIL PROTECTED] (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.
OK, updated wording:
* Allow calling of a procedure outside a SELECT that can control the
transaction state
I see now why a transaction is needed --- because it doesn't have the
SELECT wrapper.
--
Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
--
Sent via pgsql-committers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers
