Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Cannot Reproduce
-
10.3(EOL)
-
None
Description
temporary sequences don't work properly after 'ALTER engine' command, e.g.:
MariaDB [test]> create temporary sequence s; |
Query OK, 0 rows affected (0.00 sec) |
|
MariaDB [test]> alter table s engine myisam; |
Query OK, 1 row affected (0.00 sec)
|
Records: 1 Duplicates: 0 Warnings: 0
|
|
MariaDB [test]> select nextval(s); |
+-----------------+ |
| nextval(s) |
|
+-----------------+ |
| 140241957546134 |
|
+-----------------+ |
1 row in set (0.00 sec) |
|
MariaDB [test]> \r
|
Connection id: 16 |
Current database: test |
|
MariaDB [test]> create temporary sequence s; |
Query OK, 0 rows affected (0.00 sec) |
|
MariaDB [test]> alter table s engine innodb; |
Query OK, 1 row affected (0.00 sec)
|
Records: 1 Duplicates: 0 Warnings: 0
|
|
MariaDB [test]> select nextval(s); |
+------------+ |
| nextval(s) |
|
+------------+ |
| 0 |
|
+------------+ |
1 row in set (0.00 sec) |
|
MariaDB [test]> select nextval(s); |
+-----------------+ |
| nextval(s) |
|
+-----------------+ |
| 140241957547216 |
|
+-----------------+ |
1 row in set (0.00 sec) |
Attachments
Issue Links
- relates to
-
MDEV-12930 Testing SEQUENCE object
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Link |
This issue relates to |
Component/s | Sequences [ 14009 ] |
Fix Version/s | 10.3 [ 22126 ] | |
Fix Version/s | 10.4 [ 22408 ] | |
Priority | Minor [ 4 ] | Major [ 3 ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
issue.field.resolutiondate | 2018-05-07 13:41:46.0 | 2018-05-07 13:41:46.236 |
Fix Version/s | 10.3.7 [ 23005 ] | |
Fix Version/s | 10.3 [ 22126 ] | |
Resolution | Cannot Reproduce [ 5 ] | |
Status | In Progress [ 3 ] | Closed [ 6 ] |
Workflow | MariaDB v3 [ 81116 ] | MariaDB v4 [ 152274 ] |
Looks like the bug was fixed some time ago (at least I can't repeat it).
I added the test case just have this case tested properly.