Practical technology learning
SQL Transactions: Rehearse an Update and Rollback in a Disposable PostgreSQL Lab
A successful UPDATE message tells you that a statement ran. It does not tell you whether the transaction was committed. A small disposable PostgreSQL exercise can make that distinction concrete without touching business data.
Establish a disposable boundary
Use a local practice database that you are allowed to recreate. Create a separate table named practice_stock with item_id as an integer primary key and quantity as an integer. Insert two synthetic rows: item 1 with quantity 12 and item 2 with quantity 7. Finish that setup before starting the exercise transaction.
The lab extends CRUD learning, a useful foundation for SQL course learners in Jaipur. PostgreSQL is the chosen example engine; do not assume identical behaviour for every database or client tool.
Read the baseline before editing
In one identified SQL session, run SELECT item_id, quantity FROM practice_stock ORDER BY item_id. Save the result and your expected change. The intended update is only item 1, from 12 to 9; item 2 should remain 7. Check the WHERE condition with a SELECT before writing the UPDATE.
Observe an uncommitted change
Run BEGIN, then UPDATE practice_stock SET quantity = 9 WHERE item_id = 1. Query the same two rows again in that same session. You should see 9 and 7 while the transaction is still open. That observation is not a claim that another session can already see the change.
Keep the exercise short. An open transaction can retain locks and interfere with other work. Do not leave the session idle while treating the practice table as a shared service.
Roll back and compare
Issue ROLLBACK and repeat the ordered SELECT. The original values, 12 and 7, should return. Keep the before, inside-transaction and after-rollback results together. In a second deliberate run, you could choose COMMIT instead, then check the retained value and reset the disposable fixture.
Name the limits of the rehearsal
- Verify whether your client wraps statements in transactions or uses autocommit.
- If a statement puts the transaction into an error state, roll it back before continuing the simple lab.
- Rollback is not a universal undo for committed work, external messages, sequence changes or every possible side effect.
Review the evidence, not only the command
Write the database engine, session, transaction boundary, selected row and expected final value in your notes. If the final SELECT differs, stop and explain the mismatch before trying another update. The related Mango Engineers SQL learning path covers broader relational practice; confirm current course details separately.