{"id":107976,"date":"2018-01-09T09:05:49","date_gmt":"2018-01-09T09:05:49","guid":{"rendered":"https:\/\/webkul.com\/blog\/?p=107976"},"modified":"2018-01-10T07:28:27","modified_gmt":"2018-01-10T07:28:27","slug":"using-transactions-joomla-maintaining-acid-property","status":"publish","type":"post","link":"https:\/\/webkul.com\/blog\/using-transactions-joomla-maintaining-acid-property\/","title":{"rendered":"Using Transactions In Joomla to maintaining ACID Property"},"content":{"rendered":"

Using Transactions In Joomla to maintaining ACID Property: A transaction is a very small unit of a program and it may contain several lowlevel tasks. A transaction in a database system must maintain Atomicity, Consistency, Isolation, and Durability \u2212 commonly known as ACID properties \u2212 in order to ensure accuracy, completeness, and data integrity.<\/p>\n

\n
\n
\n

Atomicity :<\/h3>\n<\/div>\n<\/div>\n
\n
A transaction must be an atomic unit of work; either all of its data modifications are performed, or none of them is performed.<\/div>\n<\/div>\n<\/div>\n
\n
\n
\n

Consistency :<\/h3>\n<\/div>\n<\/div>\n
\n
When completed, a transaction must leave all data in a consistent state. In a relational database, all rules must be applied to the transaction’s modifications to maintain all data integrity. All internal data structures, such as B-tree indexes or doubly-linked lists, must be correct at the end of the transaction.<\/div>\n<\/div>\n<\/div>\n
\n
\n
\n

Isolation :<\/h3>\n<\/div>\n<\/div>\n
\n
Modifications made by concurrent transactions must be isolated from the modifications made by any other concurrent transactions. A transaction either recognizes data in the state it was in before another concurrent transaction modified it, or it recognizes the data after the second transaction has completed, but it does not recognize an intermediate state.<\/div>\n<\/div>\n<\/div>\n
\n
\n
\n

Durability :<\/h3>\n<\/div>\n<\/div>\n
\n
After a transaction has completed, its effects are permanently in place in the system. The modifications persist even in the event of a system failure.<\/div>\n<\/div>\n<\/div>\n
\n
\n
\n

Example<\/h3>\n<\/div>\n<\/div>\n
\n
\n

This will play an important role where we have to perform operations on more than one table at a time.<\/p>\n

eg: we have 4 separate Insert query for 4 different tables and we want that if any one of query fails, then all query must be rollback. i.e. either all 4 query execute successfully or none of them.<\/p>\n

\/**\r\n * Webkul Software.\r\n *\r\n * @category Webkul\r\n * @author Webkul <support@webkul.com>\r\n * @copyright Copyright (c) 2010-2018 Webkul Software Private Limited\r\n * @license https:\/\/store.webkul.com\/license.html\r\n *\/\r\n \/\/to get instance of JDatabaseDriver class\r\n $db=JFactory::getDBO();\r\n try {\r\n  \/\/Method to initialize a transaction\r\n  $db->transactionStart();\r\n  \/\/initialize JDatabaseQuery object for query\r\n  $query1=$db->getQuery(true);\r\n  $values = array($db->quote('VALUE_1'),\r\n                  $db->quote('VALUE_2'),\r\n                  $db->quote('VALUE_3'));\r\n  $query->insert($db->quoteName('#__YOUR_TABLE'));\r\n  $query->columns($db->quoteName(\r\n                 array('FIELD_1',\r\n                       'FIELD_2', \r\n                       'FIELD_3')));\r\n  $query->values(implode(',',$values));\r\n  $db->setQuery($query);\r\n  $result = $db->execute();\r\n  \/\/It is used to commit Transaction. \r\n  $db->transactionCommit();  \r\n }\r\n catch (Exception $e) {\r\n  \/\/ catch any database errors.\r\n  \/\/It is used to rollback Transactions if query fails.\r\n  $db->transactionRollback();\r\n  JErrorPage::render($e);\r\n }\r\n<\/pre>\n<\/div>\n<\/div>\n<\/div>\n
\n
\n
\n
Conclusion:<\/h3>\n<\/div>\n<\/div>\n
\n
\n