Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Won't Fix
-
10.3.0
Description
Oracle example hr ddl script has following command:
CREATE SEQUENCE EMPLOYEES_SEQ |
INCREMENT BY 1 |
MAXVALUE 9999999999999999999999999999
|
MINVALUE 1
|
NOCACHE
|
;
|
Which fails in 10.3.0 with sql_mode='oracle'::
MariaDB [test]> CREATE SEQUENCE EMPLOYEES_SEQ
|
-> INCREMENT BY 1
|
-> MAXVALUE 9999999999999999999999999999
|
-> MINVALUE 1
|
-> NOCACHE
|
-> ;
|
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '9999999999999999999999999999
|
MINVALUE 1
|
NOCACHE' at line 3
|
The command succeeds when MAXVALUE is reduced down to 18x9s, i.e.:
MariaDB [test]> create sequence d18 maxvalue 999999999999999999;
|
Query OK, 0 rows affected (0.03 sec)
|
|
|
MariaDB [test]> create sequence d19 maxvalue 9999999999999999999;
|
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '9999999999999999999' at line 1
|
I am not sure that we should implement sequence with such high range, but we definitely should make sure that such commands succeed (maybe with a warning that maxvalue was adjusted). That should simplify typical migration and eventual testing with existing scripts.
Attachments
Issue Links
- relates to
-
MDEV-10139 Support for SEQUENCE objects
-
- Closed
-
-
MDEV-12533
sql_mode=ORACLE: Add support for database qualified sequence names in NEXTVAL and CURRVAL
-
- Closed
-
Activity
| Transition | Time In Source Status | Execution Times |
|---|
|
317d 14h 45m | 1 |
|
49s | 1 |