Public bug reported:
0. mariadb version (aws rds) :
mysql> select @@version;
+-+
| @@version |
+-+
| 10.11.7-MariaDB-log |
+-+
1 row in set (0.00 sec)
pt-osc version
[ec2-user@ip-10-0-0-32 ~]$ pt-online-schema-change --version
Need to remove constraints from the test table ddl script that I gave you first.
And I think the table name needs to be changed too.
CREATE TABLE `bjh`.`test` (
`MSHP_ID` varchar(16) NOT NULL ,
`STR_CD` varchar(7) NOT NULL ,
`SAVE_PNT` decimal(15,3) DEFAULT NULL ,
`USE_PNT` decimal(15,3) DE
Need to remove constraints from the test table ddl script that I gave you first.
And I think the table name needs to be changed too.
CREATE TABLE `bjh`.`test` (
`MSHP_ID` varchar(16) NOT NULL ,
`STR_CD` varchar(7) NOT NULL ,
`SAVE_PNT` decimal(15,3) DEFAULT NULL ,
`USE_PNT` decimal(15,3) DE
** Description changed:
0. mariadb version (aws rds) :
mysql> select @@version;
+-+
| @@version |
+-+
| 10.11.7-MariaDB-log |
+-+
1 row in set (0.00 sec)
pt-osc version
[ec2-user@ip-10-0-0-32 ~]$ pt-onl
I modified the above test scenario to make it simpler and modified the
DDL, procedure, and pt-online-schema-change script to specifically check
whether the trigger really working during the pt-osc process operates.
1-1. Table DDL Script
CREATE TABLE `test1` (
`seq` bigint unsigned not null AUTO_
