Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.3.0
-
None
Description
All MySQL-specific dialect expressions must work in sql_mode=oracle , (unless they really conflict with Oracle syntax - but then it may be serious limitation for some cases).
The reasoning behind that is that some 10.2 environments may rely on that dialect with sql_mode=oracle and it may be very unfortunate if those stop working after upgrading to 10.3 .
As example I could identify following cases in MDEV-12962 :
1. ELSEIF stopped working in sql_mode=oracle, which recognising only ELSIF now
2. '%' operator has gone in sql_mode=oracle (see MDEV-12977)
Other cases must be considered as well in 10.3 oracle parser during testing / implementation.
Attachments
Issue Links
- relates to
-
MDEV-12962 Testing MDEV-10142 (PL/SQL parser)
-
- Open
-
Activity
Field | Original Value | New Value |
---|---|---|
Link | This issue relates to MDEV-12962 [ MDEV-12962 ] |
Fix Version/s | 10.4 [ 22408 ] |
Workflow | MariaDB v3 [ 81951 ] | MariaDB v4 [ 140382 ] |
Fix Version/s | 10.3 [ 22126 ] |