pgsql: Changed TODO wording: < * Support procedures, which return no
Log Message:
-----------
Changed TODO wording:
< * Support procedures, which return no value
* Allow functions to control the transaction state
Modified Files:
--------------
pgsql/doc:
TODO (r1.2413 -> r1.2414)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/TODO?r1=1.2413&r2=1.2414)
pgsql/doc/src/FAQ:
TODO.html (r1.919 -> r1.920)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html?r1=1.919&r2=1.920)
momjian@postgresql.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
Tom Lane wrote:
momjian@postgresql.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.
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 <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +