MySql Tutorial

MySQL general security issues

Here, in this section you will study about different general security issues in MySQL. Security Guidelines Always keep in mind the following security guidelines before working with MySQL. Do not permit or allow anyone to access the user table in mysql database, except the MySQL root account. Always use GRANT and REVOKE statements to control access to …

MySQL general security issues Read More »

The MySQL Access Privilege System

Here, in this section you will study about different Access Privilege Systems. Privileges Provided by MySQL Here, MySQL provides privileges that apply in different contexts and at different levels of operation: Administrative privileges allow users to manage operation of the MySQL server. These privileges are global because they are not specific to a particular database. …

The MySQL Access Privilege System Read More »

MySQL and the ACID Model

ACID stands for Atomicity, Consistency, Isolation and Durability. It is a set of properties that guarantee that database transactions are processed reliably. In MySQL, InnoDB storage engine supports ACID-compliant features. Atomicity: The atomicity aspect of the ACID model mainly involves InnoDB transactions. MySQL features include: Autocommit setting. COMMIT statement. ROLLBACK statement. Operational data from the INFORMATION_SCHEMA …

MySQL and the ACID Model Read More »

MySQL Transaction

MySQL in version 5.6 supports local transactions means within a given client session through statements such as SET autocommit, START TRANSACTION, COMMIT, and ROLLBACK. Syntax of START TRANSACTION, COMMIT, and ROLLBACK: START TRANSACTION transaction_characteristic [, transaction_characteristic] …] transaction_characteristic: WITH CONSISTENT SNAPSHOT | READ WRITE | READ ONLY BEGIN [WORK] COMMIT [WORK] [AND [NO] CHAIN] [[NO] …

MySQL Transaction Read More »

MySQL statements that cannot be Rolled Back and statements that cause an implicit Commit

In MySQL some statements cannot be rolled back. DDL statements such as CREATE or DROP databases, CREATE, ALTER or DROP tables or stored routines. You should design a transaction without these statements. The statements listed below implicitly end any transaction active in the current session, as if you had done a COMMIT before executing the …

MySQL statements that cannot be Rolled Back and statements that cause an implicit Commit Read More »

SAVEPOINT, ROLLBACK TO SAVEPOINT, and RELEASE SAVEPOINT

InnoDB supports the SQL statements SAVEPOINT, ROLLBACK TO SAVEPOINT, RELEASE SAVEPOINT and the optional WORK keyword for ROLLBACK. The SAVEPOINT statement sets a named transaction savepoint with a name of identifier. If the current transaction has a savepoint with the same name, the old savepoint is deleted and a new one is set. The ROLLBACK TO SAVEPOINT statement rolls …

SAVEPOINT, ROLLBACK TO SAVEPOINT, and RELEASE SAVEPOINT Read More »

LOCK and UNLOCK Tables

MySQL allows client sessions to acquire table locks explicitly for the purpose of cooperating with other sessions for access to tables, or to prevent other sessions from modifying tables during periods when a session requires exclusive access to them. A session can acquire or release locks only for itself. One session cannot acquire locks for …

LOCK and UNLOCK Tables Read More »

SET TRANSACTION Syntax

SET [GLOBAL | SESSION] TRANSACTION transaction_characteristic [, transaction_characteristic] … transaction_characteristic: ISOLATION LEVEL level | READ WRITE | READ ONLY level: REPEATABLE READ | READ COMMITTED | READ UNCOMMITTED | SERIALIZABLE Let us describe you the Syntax in brief: With the GLOBAL keyword, the statement applies globally for all subsequent sessions. Existing sessions are unaffected. With …

SET TRANSACTION Syntax Read More »

Scroll to Top