From 5e45211a64149b3c659b90ff2de6fa982a5a93ed Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sat, 4 May 2024 14:17:33 +0200 Subject: Adding upstream version 15.5. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/pltcl-transactions.html | 33 +++++++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) create mode 100644 doc/src/sgml/html/pltcl-transactions.html (limited to 'doc/src/sgml/html/pltcl-transactions.html') diff --git a/doc/src/sgml/html/pltcl-transactions.html b/doc/src/sgml/html/pltcl-transactions.html new file mode 100644 index 0000000..7be56f6 --- /dev/null +++ b/doc/src/sgml/html/pltcl-transactions.html @@ -0,0 +1,33 @@ + +44.10. Transaction Management
44.10. Transaction Management
Prev UpChapter 44. PL/Tcl — Tcl Procedural LanguageHome Next

44.10. Transaction Management

+ In a procedure called from the top level or an anonymous code block + (DO command) called from the top level it is possible + to control transactions. To commit the current transaction, call the + commit command. To roll back the current transaction, + call the rollback command. (Note that it is not + possible to run the SQL commands COMMIT or + ROLLBACK via spi_exec or similar. + It has to be done using these functions.) After a transaction is ended, + a new transaction is automatically started, so there is no separate + command for that. +

+ Here is an example: +

+CREATE PROCEDURE transaction_test1()
+LANGUAGE pltcl
+AS $$
+for {set i 0} {$i < 10} {incr i} {
+    spi_exec "INSERT INTO test1 (a) VALUES ($i)"
+    if {$i % 2 == 0} {
+        commit
+    } else {
+        rollback
+    }
+}
+$$;
+
+CALL transaction_test1();
+

+

+ Transactions cannot be ended when an explicit subtransaction is active. +

Prev Up Next
44.9. Explicit Subtransactions in PL/Tcl Home 44.11. PL/Tcl Configuration
\ No newline at end of file -- cgit v1.2.3