395 10.1.6. Internal Savepoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396 10.1.7. Savepoints and PSQL . . . . . . . rdb$set_context('USER_SESSION', 'RecordsFound', RecCounter); select rdb$set_context('USER_TRANSACTION', 'Savepoints', 'Yes') from rdb$database Notes • The maximum number of variables in any single context is variables set with RDB$SET_CONTEXT() remain unchanged. • Any savepoints that were created after the one named are destroyed. Savepoints earlier than the one named are preserved, along with the named

567 12.1.6. Internal Savepoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568 12.1.7. Savepoints and PSQL . . . . . . . rdb$set_context('USER_SESSION', 'RecordsFound', RecCounter); select rdb$set_context('USER_TRANSACTION', 'Savepoints', 'Yes') from rdb$database See also RDB$GET_CONTEXT() 8.2. Mathematical Functions 8.2.1. variables set with RDB$SET_CONTEXT() remain unchanged. • Any savepoints that were created after the one named are destroyed. Savepoints earlier than the one named are preserved, along with the named

control the statements in a transaction in a more granular fashion through the use of save- points. Savepoints allow you to selectively discard parts of the transaction, while committing the rest. After defining Keep in mind that either releasing or rolling back to a savepoint will automatically release all savepoints that were defined after it. All this is happening within the transaction block, so none of it ac- count, only to find later that we should have credited Wally’s account. We could do it using savepoints like this: BEGIN; UPDATE accounts SET balance = balance - 100.00 WHERE name = ’Alice’; SAVEPOINT

to control the statements in a transaction in a more granular fashion through the use of savepoints. Savepoints allow you to selectively discard parts of the transaction, while committing the rest. After Keep in mind that either releasing or rolling back to a savepoint will automatically release all savepoints that were defined after it. All this is happening within the transaction block, so none of it oversimplified, but there’s a lot of control to be had over a transaction block through the use of savepoints. Moreover, ROLLBACK TO is the only way to regain control of a transaction block that was put in

control the statements in a transaction in a more granular fashion through the use of save- points. Savepoints allow you to selectively discard parts of the transaction, while committing the rest. After defining Keep in mind that either releasing or rolling back to a savepoint will automatically release all savepoints that were defined after it. All this is happening within the transaction block, so none of it ac- count, only to find later that we should have credited Wally’s account. We could do it using savepoints like this: BEGIN; UPDATE accounts SET balance = balance - 100.00 WHERE name = ’Alice’; SAVEPOINT

control the statements in a transaction in a more granular fashion through the use of save- points. Savepoints allow you to selectively discard parts of the transaction, while committing the rest. After defining Keep in mind that either releasing or rolling back to a savepoint will automatically release all savepoints that were defined after it. All this is happening within the transaction block, so none of it ac- count, only to find later that we should have credited Wally’s account. We could do it using savepoints like this: BEGIN; UPDATE accounts SET balance = balance - 100.00 WHERE name = ’Alice’; SAVEPOINT

control the statements in a transaction in a more granular fashion through the use of save- points. Savepoints allow you to selectively discard parts of the transaction, while committing the rest. After defining Keep in mind that either releasing or rolling back to a savepoint will automatically release all savepoints that were defined after it. All this is happening within the transaction block, so none of it ac- count, only to find later that we should have credited Wally’s account. We could do it using savepoints like this: BEGIN; UPDATE accounts SET balance = balance - 100.00 WHERE name = ’Alice’; SAVEPOINT

Interface 767 Using the ResultSetHandle Interface 768 Using JDBC 769 Exception Handling 769 Savepoints 770 Logging 770 Security 770 Installation 771 Trusted Language 771 Some PL/Java Issues and 1781 pljava_classpath_insecure 1782 pljava_statement_cache_size 1782 pljava_release_lingering_savepoints 1782 pljava_vmoptions 1782 port 1782 quote_all_identifiers 1783 random_page_cost 1783 rea Installing JAR Files Uninstalling PL/Java Writing PL/Java functions Using JDBC Exception Handling Savepoints Logging Security Some PL/Java Issues and Solutions Example References About PL/Java VMware

VMware Greenplum v6.18 Documentation VMware, Inc. 21 Using JDBC 441 Exception Handling 442 Savepoints 442 Logging 442 Security 0 Installation 443 Trusted Language 443 Some PL/Java Issues and Solutions 1632 pljava_classpath_insecure 1632 pljava_statement_cache_size 1633 pljava_release_lingering_savepoints 1633 pljava_vmoptions 1633 port 1634 quote_all_identifiers 1634 random_page_cost 1634 rea Installing JAR Files Uninstalling PL/Java Writing PL/Java functions Using JDBC Exception Handling Savepoints Logging Security Some PL/Java Issues and Solutions Example References VMware Greenplum v6

Interface 449 Using the ResultSetHandle Interface 450 Using JDBC 451 Exception Handling 451 Savepoints 452 VMware Greenplum v6.19 Documentation VMware, Inc. 22 Logging 452 Security 0 Installation 1642 pljava_classpath_insecure 1643 pljava_statement_cache_size 1644 pljava_release_lingering_savepoints 1644 pljava_vmoptions 1644 port 1644 VMware Greenplum v6.19 Documentation VMware, Inc. 118 functions Using JDBC Exception Handling VMware Greenplum v6.19 Documentation VMware, Inc. 436 Savepoints Logging Security Some PL/Java Issues and Solutions Example References About PL/Java With