Should I commit or rollback a read transaction?

by

You commit. Period. There’s no other sensible alternative. If you started a transaction, you should close it. Committing releases any locks you may have had, and is equally sensible with ReadUncommitted or Serializable isolation levels. Relying on implicit rollback – while perhaps technically equivalent – is just poor form.

If that hasn’t convinced you, just imagine the next guy who inserts an update statement in the middle of your code, and has to track down the implicit rollback that occurs and removes his data.

More Related Contents:

  1. Correct use of transactions in SQL Server
  2. Do database transactions prevent race conditions?
  3. Continuing a transaction after primary key violation error
  4. ‘Lost update’ vs ‘Write skew’
  5. What’s the best practice for primary keys in tables? [closed]
  6. What are best practices for multi-language database design? [closed]
  7. What is atomicity in dbms
  8. SQLite – How do you join tables from different databases?
  9. MySQL dump by query
  10. SQL ROWNUM how to return rows between a specific range
  11. How would you implement sequences in Microsoft SQL Server?
  12. SQL how to compare two tables for same data content?
  13. What does =* mean?
  14. Does MS Access support “CASE WHEN” clause if connect with ODBC?
  15. MySQL equivalent of DECODE function in Oracle
  16. What datatype to use when storing latitude and longitude data in SQL databases? [duplicate]
  17. Why do NULL values come first when ordering DESC in a PostgreSQL query?
  18. Favourite performance tuning tricks [closed]
  19. How do I alter the position of a column in a PostgreSQL database table?
  20. Is it necessary to create tables each time you connect the derby database?
  21. Venn Diagram for Natural Join
  22. Database efficiency – table per user vs. table of users
  23. SQL ON DELETE CASCADE, Which Way Does the Deletion Occur?
  24. Find rows that have the same value on a column in MySQL
  25. what is the difference between GROUP BY and ORDER BY in sql
  26. The ORDER BY clause is invalid in views, inline functions, derived tables, subqueries, and common table expressions
  27. Relational Data Model for Double-Entry Accounting
  28. Creating a custom ODBC driver
  29. Do conditional INSERT with SQL?
  30. ORA-01652: unable to extend temp segment by 128 in tablespace SYSTEM: How to extend?

Leave a Comment