Transaction Management
Learn about Auto Commit, manual Commit/Rollback, and how to check execution results.
Auto Commit Toggle
Use the Auto Commit switch in the Toolbar to toggle automatic commit mode on and off.
| Mode | Behavior |
|---|---|
| Auto Commit ON (default) | Each SQL statement is automatically committed immediately after execution. No separate Commit/Rollback action is needed. |
| Auto Commit OFF | You must manually Commit or Rollback after executing SQL. Commit and Rollback buttons appear in the Toolbar. |
In MySQL, MariaDB, and Oracle, DDL statements (CREATE, ALTER, DROP, etc.) are implicitly committed regardless of the Auto Commit setting. In PostgreSQL and SQL Server, DDL can be rolled back within a transaction.
Manual Commit
When Auto Commit is off, clicking the Commit button in the Toolbar permanently applies all uncommitted changes in the current session to the database.
When a commit is needed, the
Rollback
When Auto Commit is off, clicking the Rollback button in the Toolbar cancels all uncommitted changes in the current session. Data is restored to its state before SQL execution.
If you accidentally modified data, you can undo it with Rollback. However, if Auto Commit is on, changes are committed immediately and cannot be rolled back. We recommend turning off Auto Commit when modifying important data.
Execution Time / Row Count
After query execution completes, the following information is displayed in the status bar of the result area:
| Item | Description |
|---|---|
| Row count | Number of rows returned (SELECT) or affected (DML) |
| Execution time | Time taken to execute the query (in milliseconds) |
| (truncated) | Displayed when the result is truncated due to reaching the maximum row limit |