Details
-
Technical task
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
-
None
Description
When running with sql_mode=ORACLE, MariaDB should emulate Oracle-style transaction related behavior:
- No explicit transaction start (e.g. BEGIN or START statement) is needed.
Transactions start automatically and last until COMMIT or ROLLBACK.
This looks to be equal to SET AUTOCOMMIT=0.
- The BEGIN keyword should always start a code block (a compound statement), even outside of a stored procedure.
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Description |
When running with {{sql_mode=ORACLE}}, MariaDB should emulate Oracle-style transaction related behavior:
- No explicit transaction start (e.g. {{BEGIN}} or {{START}} statement) is needed. Transactions start automatically and last until {{COMMIT}} or {{ROLLBACK}}. - The {{BEGIN}} keyword should always start a code block, even outside of a stored procedure. |
When running with {{sql_mode=ORACLE}}, MariaDB should emulate Oracle-style transaction related behavior:
- No explicit transaction start (e.g. {{BEGIN}} or {{START}} statement) is needed. Transactions start automatically and last until {{COMMIT}} or {{ROLLBACK}}. This looks to be equal to {{SET AUTOCOMMIT=1}}. - The {{BEGIN}} keyword should always start a code block, even outside of a stored procedure. |
| Link | This issue is part of MDEV-10137 [ MDEV-10137 ] |
| Description |
When running with {{sql_mode=ORACLE}}, MariaDB should emulate Oracle-style transaction related behavior:
- No explicit transaction start (e.g. {{BEGIN}} or {{START}} statement) is needed. Transactions start automatically and last until {{COMMIT}} or {{ROLLBACK}}. This looks to be equal to {{SET AUTOCOMMIT=1}}. - The {{BEGIN}} keyword should always start a code block, even outside of a stored procedure. |
When running with {{sql_mode=ORACLE}}, MariaDB should emulate Oracle-style transaction related behavior:
- No explicit transaction start (e.g. {{BEGIN}} or {{START}} statement) is needed. Transactions start automatically and last until {{COMMIT}} or {{ROLLBACK}}. This looks to be equal to {{SET AUTOCOMMIT=1}}. - The {{BEGIN}} keyword should always start a code block (a compound statement), even outside of a stored procedure. |
| Link | This issue is part of MDEV-10137 [ MDEV-10137 ] |
| Parent |
|
|
| Issue Type | Task [ 3 ] | Technical task [ 7 ] |
| Labels | Compatibility |
| Labels | Compatibility |
| Link |
This issue blocks |
| Labels | Compatibility |
| Labels | Compatibility |
| Description |
When running with {{sql_mode=ORACLE}}, MariaDB should emulate Oracle-style transaction related behavior:
- No explicit transaction start (e.g. {{BEGIN}} or {{START}} statement) is needed. Transactions start automatically and last until {{COMMIT}} or {{ROLLBACK}}. This looks to be equal to {{SET AUTOCOMMIT=1}}. - The {{BEGIN}} keyword should always start a code block (a compound statement), even outside of a stored procedure. |
When running with {{sql_mode=ORACLE}}, MariaDB should emulate Oracle-style transaction related behavior:
- No explicit transaction start (e.g. {{BEGIN}} or {{START}} statement) is needed. Transactions start automatically and last until {{COMMIT}} or {{ROLLBACK}}. This looks to be equal to {{SET AUTOCOMMIT=0}}. - The {{BEGIN}} keyword should always start a code block (a compound statement), even outside of a stored procedure. |
| Summary | Automatic transaction start for sql_mode=ORACLE | Automatic transaction start for sql_mode=ORACLE |
| Labels | Compatibility |
| Labels | Compatibility | Compatibility NRE-307517 |
| NRE Projects | NRE-307517 |
| Labels | Compatibility NRE-307517 | Compatibility |
| Fix Version/s | 10.3 [ 22126 ] | |
| Fix Version/s | 10.2 [ 14601 ] |
| Comment | [ Should it have 10.2 as a fix version? ] |
| Parent |
|
MDEV-10764 [ 57940 ] |
| Fix Version/s | 10.3 [ 22126 ] |
| Support case ID | not-26307 |
| NRE Projects | AC-2610/DEFERRED |
| Link |
This issue blocks |
| Workflow | MariaDB v3 [ 76677 ] | MariaDB v4 [ 140035 ] |