MySQL - Transactions

A transaction is a sequential group of database manipulation operations, which is performed as if it were one single work unit. In other words, a transaction will never be complete unless each individual operation within the group is successful. If any operation within the transaction fails, the entire transaction will fail.
Practically, you will club many SQL queries into a group and you will execute all of them together as a part of a transaction.
Transactions have the following four standard properties, usually referred to by the acronym ACID −
Atomicity − This ensures that all operations within the work unit are completed successfully; otherwise, the transaction is aborted at the point of failure and previous operations are rolled back to their former state.
Atomicity − This ensures that all operations within the work unit are completed successfully; otherwise, the transaction is aborted at the point of failure and previous operations are rolled back to their former state.
Consistency − This ensures that the database properly changes states upon a successfully committed transaction.
Consistency − This ensures that the database properly changes states upon a successfully committed transaction.
Isolation − This enables transactions to operate independently on and transparent to each other.
Isolation − This enables transactions to operate independently on and transparent to each other.
Durability − This ensures that the result or effect of a committed transaction persists in case of a system failure.
Durability − This ensures that the result or effect of a committed transaction persists in case of a system failure.
In MySQL, the transactions begin with the statement BEGIN WORK and end with either a COMMIT or a ROLLBACK statement. The SQL commands between the beginning and ending statements form the bulk of the transaction.
These two keywords Commit and Rollback are mainly used for MySQL Transactions.
When a successful transaction is completed, the COMMIT command should be issued so that the changes to all involved tables will take effect.
When a successful transaction is completed, the COMMIT command should be issued so that the changes to all involved tables will take effect.
If a failure occurs, a ROLLBACK command should be issued to return every table referenced in the transaction to its previous state.
If a failure occurs, a ROLLBACK command should be issued to return every table referenced in the transaction to its previous state.
You can control the behavior of a transaction by setting session variable called AUTOCOMMIT. If AUTOCOMMIT is set to 1 (the default), then each SQL statement (within a transaction or not) is considered a complete transaction and committed by default when it finishes.
When AUTOCOMMIT is set to 0, by issuing the SET AUTOCOMMIT = 0 command, the subsequent series of statements acts like a transaction and no activities are committed until an explicit COMMIT statement is issued.
You can execute these SQL commands in PHP by using the mysql_query() function.
This sequence of events is independent of the programming language used. The logical path can be created in whichever language you use to create your application.
You can execute these SQL commands in PHP by using the mysql_query() function.
Begin transaction by issuing the SQL command BEGIN WORK.
Begin transaction by issuing the SQL command BEGIN WORK.
Issue one or more SQL commands like SELECT, INSERT, UPDATE or DELETE.
Issue one or more SQL commands like SELECT, INSERT, UPDATE or DELETE.
Check if there is no error and everything is according to your requirement.
Check if there is no error and everything is according to your requirement.
If there is any error, then issue a ROLLBACK command, otherwise issue a COMMIT command.
If there is any error, then issue a ROLLBACK command, otherwise issue a COMMIT command.
You cannot use transactions directly, but for certain exceptions you can. However, they are not safe and guaranteed. If you plan to use transactions in your MySQL programming, then you need to create your tables in a special way. There are many types of tables, which support transactions, but the most popular one is InnoDB.
Support for InnoDB tables requires a specific compilation parameter when compiling MySQL from the source. If your MySQL version does not have InnoDB support, ask your Internet Service Provider to build a version of MySQL with support for InnoDB table types or download and install the MySQL-Max Binary Distribution for Windows or Linux/UNIX and work with the table type in a development environment.
If your MySQL installation supports InnoDB tables, simply add a TYPE = InnoDB definition to the table creation statement.
For example, the following code creates an InnoDB table called tcount_tbl −
root@host# mysql -u root -p password;
Enter password:*******

mysql> use TUTORIALS;
Database changed

mysql> create table tcount_tbl
   -> (
   -> tutorial_author varchar(40) NOT NULL,
   -> tutorial_count  INT
   -> ) TYPE = InnoDB;
Query OK, 0 rows affected (0.05 sec)
For more details on InnoDB, you can click on the following link −InnoDB
You can use other table types like GEMINI or BDB, but it depends on your installation, whether it supports these two table types or not.

    31 Lectures 
     6 hours 

 Eduonix Learning Solutions

    84 Lectures 
     5.5 hours 

 Frahaan Hussain

    6 Lectures 
     3.5 hours 

 DATAhill Solutions Srinivas Reddy

    60 Lectures 
     10 hours 

 Vijay Kumar Parvatha Reddy

    10 Lectures 
     1 hours 

 Harshit Srivastava

    25 Lectures 
     4 hours 

 Trevoir Williams
 Print
 Add Notes
 Bookmark this page