Difference between revisions of "Transaction Isolation"
From AgileApps Support Wiki
imported>Aeric (Created page with 'In database systems, isolation is a property that defines how/when the changes made by one operation become visible to other concurrent operations. Isolation is one of the ACID p…') |
imported>Aeric |
||
| Line 6: | Line 6: | ||
''Learn More'': | ''Learn More'': | ||
:* Transaction Isolation (<tt>tx_isolation</tt>):<br/>http://dev.mysql.com/doc/refman/ | :* Transaction Isolation (<tt>tx_isolation</tt>):<br/>http://dev.mysql.com/doc/refman/{{MySqlVersion}}/en/server-system-variables.html#sysvar_tx_isolation | ||
[[Category:Glossary]] | [[Category:Glossary]] | ||
Latest revision as of 02:33, 19 March 2014
In database systems, isolation is a property that defines how/when the changes made by one operation become visible to other concurrent operations. Isolation is one of the ACID properties.
When Transaction Isolation is set to READ UNCOMMITTED, dirty reads are allowed--so one transaction can see uncommitted changes made by some other transaction.
For system where data integrity is very critical (for example banks and financial institutions) READ COMMITTED is used, to provide a higher level of data integrity.
Learn More:
- Transaction Isolation (tx_isolation):
http://dev.mysql.com/doc/refman/5.5/en/server-system-variables.html#sysvar_tx_isolation
- Transaction Isolation (tx_isolation):