-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
As Tom has pointed out today, I've began reading the docs. plpgsql.sgml
says that PostgreSQL does not support nested transactions. I've removed
that part and a small diff is attached.
I'll be on 10-days' holiday and I'll try to read the whole docs.
Regards,
- --
Devrim GUNDUZ
devrim~gunduz.org devrim.gunduz~linux.org.tr
http://www.tdmsoft.com
http://www.gunduz.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQFBE9Lztl86P3SPfQ4RAtN9AKDjSR6Xlgl3ea2su1pDgOnsd1q27ACeLvT+
aeF83FCl8/3ccbCdauwt6Wg=
=Oks/
-----END PGP SIGNATURE-----
--- doc/src/sgml/plpgsql.sgml.orig 2004-08-06 12:05:10.000000000 +0300
+++ doc/src/sgml/plpgsql.sgml 2004-08-06 12:05:47.000000000 +0300
@@ -450,9 +450,7 @@
grouping statements in <application>PL/pgSQL</> with the database commands for
transaction control. <application>PL/pgSQL</>'s
<command>BEGIN</>/<command>END</> are only for grouping;
they do not start or end a transaction. Functions and trigger procedures
- are always executed within a transaction established by an outer query
- --- they cannot start or commit transactions, since
- <productname>PostgreSQL</productname> does not have nested transactions.
+ are always executed within a transaction established by an outer query.
</para>
</sect1>
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
