There are 4 modes that TRANSACTION_BACKOUT can be run in. The mode setting determines how the backout reacts to subsequent transactions that operate on any of the records it touches. The default mode is NOCASCADE which implements the following behaviour. If any of the records touched by the transaction being backed out were subsequently touched … Read more
The TRANSACTION_BACKOUT feature executes SQL to backout or undo the specific changes from the desired transactions. For example the UPDATE in the previous post is undone with this SQL statement. update “DRH”.”DEMO” set “DEMO_NAME” = ‘Demo 1’ where “DEMO_ID” = ‘1’ and “DEMO_NAME” = ‘Demo One’; The undo SQL identifies the specific record by including … Read more
Oracle’s TRANSACTION_BACKOUT function does just what it’s name implies – it backs out committed transactions. Here is an example: — Create a simple demo table SQL> CREATE TABLE demo 2 ( demo_id NUMBER NOT NULL PRIMARY KEY, 3 demo_name VARCHAR2(30) NOT NULL UNIQUE ); Table created. — Insert a record SQL> BEGIN 2 INSERT INTO … Read more
As a long tine use of Relational Databases I live by the rule that data must be stored in and retrieved from table. And those tables must have columns. But JSON plays by it’s own rules by allowing random attribute-value pairs with no consistency enforced. But the latest version of my most used database, Oracle … Read more
My blog…and backup…got corrupted.