Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
10.0.20, 5.5(EOL), 10.0(EOL), 10.1(EOL)
-
linux
Description
When DROPing and reCREATing a partitioned table using a stored procedure the 2nd attempt from the same session leads to a
"VALUES LESS THAN value must be strictly increasing for each partition"
error. When closing the connection, reconnecting, and then re-executing the procedure the CREATE works well again, but another call from the same session makes it fail once more
Minimalized test case:
DROP PROCEDURE IF EXISTS p1;
|
|
DELIMITER //
|
|
CREATE PROCEDURE p1()
|
BEGIN
|
DROP TABLE IF EXISTS t1 ;
|
|
CREATE TABLE t1 (
|
id INT PRIMARY KEY
|
)
|
PARTITION BY RANGE (id) (
|
PARTITION P1 VALUES LESS THAN (2),
|
PARTITION P2 VALUES LESS THAN (3)
|
);
|
END //
|
|
DELIMITER ;
|
|
call p1(); -- works
|
call p1(); -- fails
|
Attachments
Issue Links
- relates to
-
MDEV-7990 ERROR 1526 when procedure executed for second time ALTER TABLE partition ... pMAX values less than MAXVALUE
- Closed
- links to