Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug: (Primary/Secondary)After the character set is converted.Data on the primary database and that on the secondary database are inconsistent. #1199

Closed
3 tasks done
haitaoguan opened this issue Jan 9, 2023 · 0 comments · Fixed by #1272
Assignees
Labels
A-bug Something isn't working B-DDL DDL related issues B-master-replica master/replica sync, replay B-storage data type, data storage, insert,update,delete, transactions prio: high High priority

Comments

@haitaoguan
Copy link
Collaborator

Have you read the Contributing Guidelines on issues?

Please confirm if bug report does NOT exists already ?

  • I confirm there is no existing issue for this

Describe the problem

create table ttt(id int,name varchar(5));
insert into ttt values(1,'AAA'),(2,'BBB');
alter table ttt convert to character set utf8;
delete from ttt where id=1;
alter table ttt convert to character set utf8mb4;

###MASTER
mysql> show create table ttt\G
*************************** 1. row ***************************
       Table: ttt
Create Table: CREATE TABLE `ttt` (
  `id` int(11) DEFAULT NULL,
  `name` varchar(5) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4
1 row in set (0.00 sec)

mysql> select * from ttt;
+------+------+
| id   | name |
+------+------+
|    2 | BBB  |
+------+------+
1 row in set (0.00 sec)

###SLAVE
mysql> show create table ttt\G
*************************** 1. row ***************************
       Table: ttt
Create Table: CREATE TABLE `ttt` (
  `id` int(11) DEFAULT NULL,
  `name` varchar(5) DEFAULT NULL
) ENGINE=TIANMU DEFAULT CHARSET=utf8mb4
1 row in set (0.01 sec)

mysql> select * from ttt;
+------+------+
| id   | name |
+------+------+
| NULL | NULL |
|    2 | BBB  |
+------+------+
2 rows in set (0.00 sec)

Expected behavior

mysql> select * from ttt;
+------+------+
| id   | name |
+------+------+
|    2 | BBB  |
+------+------+
1 row in set (0.00 sec)

How To Reproduce

No response

Environment

./mysqld Ver 5.7.36-StoneDB for Linux on x86_64 (build-)
build information as follow:
Repository address: https://github.com/stoneatom/stonedb.git:stonedb-5.7-dev
Branch name: stonedb-5.7-dev
Last commit ID: 0bc2cbe
Last commit time: Date: Fri Dec 30 17:46:55 2022 +0800
Build time: Date: Tue Jan 3 09:59:43 CST 2023

Are you interested in submitting a PR to solve the problem?

  • Yes, I will!
@haitaoguan haitaoguan added the A-bug Something isn't working label Jan 9, 2023
@wisehead wisehead added this to the stonedb_5.7_v1.0.3 milestone Jan 9, 2023
@wisehead wisehead added B-master-replica master/replica sync, replay B-DDL DDL related issues labels Jan 9, 2023
@haitaoguan haitaoguan changed the title bug: between master/slave,after the character set is converted.Data on the primary database and that on the secondary database are inconsistent. bug: Primary/Secondary,after the character set is converted.Data on the primary database and that on the secondary database are inconsistent. Jan 12, 2023
@haitaoguan haitaoguan changed the title bug: Primary/Secondary,after the character set is converted.Data on the primary database and that on the secondary database are inconsistent. bug: (Primary/Secondary)After the character set is converted.Data on the primary database and that on the secondary database are inconsistent. Jan 12, 2023
@wisehead wisehead added the prio: high High priority label Jan 30, 2023
@hustjieke hustjieke added the B-storage data type, data storage, insert,update,delete, transactions label Jan 30, 2023
DandreChen added a commit to DandreChen/stonedb that referenced this issue Feb 3, 2023
…neatom#1199)

Because the records which was deleted is not filtered.
DandreChen added a commit to DandreChen/stonedb that referenced this issue Feb 3, 2023
…neatom#1199)

Because the records which was deleted is not filtered.
DandreChen added a commit to DandreChen/stonedb that referenced this issue Feb 3, 2023
…neatom#1199)

Because the records which was deleted is not filtered in fill_row().
DandreChen added a commit to DandreChen/stonedb that referenced this issue Feb 4, 2023
…neatom#1199)

Because the records which was deleted is not filtered in fill_row().
DandreChen added a commit to DandreChen/stonedb that referenced this issue Feb 4, 2023
…neatom#1199)

Because the records which was deleted is not filtered in fill_row().
DandreChen added a commit to DandreChen/stonedb that referenced this issue Feb 6, 2023
…neatom#1199)

Because the records which was deleted is not filtered in fill_row().
DandreChen added a commit to DandreChen/stonedb that referenced this issue Feb 6, 2023
…neatom#1199)

Because the records which was deleted is not filtered in fill_row().
DandreChen added a commit to DandreChen/stonedb that referenced this issue Feb 8, 2023
…neatom#1199)

Because the records which was deleted is not filtered in fill_row().
DandreChen added a commit to DandreChen/stonedb that referenced this issue Feb 8, 2023
…neatom#1199)

Because the records which was deleted is not filtered in fill_row().
DandreChen added a commit to DandreChen/stonedb that referenced this issue Feb 14, 2023
…neatom#1199)

Because the records which was deleted is not filtered in fill_row().
DandreChen added a commit to DandreChen/stonedb that referenced this issue Feb 14, 2023
…neatom#1199)

Because the records which was deleted is not filtered in fill_row().
DandreChen added a commit to DandreChen/stonedb that referenced this issue Feb 15, 2023
…neatom#1199)

Because the records which was deleted is not filtered in fill_row().
DandreChen added a commit to DandreChen/stonedb that referenced this issue Feb 16, 2023
…neatom#1199)

Because the records which was deleted is not filtered in fill_row().
DandreChen added a commit to DandreChen/stonedb that referenced this issue Feb 16, 2023
…neatom#1199)

Because the records which was deleted is not filtered in fill_row().
mergify bot pushed a commit that referenced this issue Feb 16, 2023
Because the records which was deleted is not filtered in fill_row().
@mergify mergify bot closed this as completed in #1272 Feb 16, 2023
mergify bot pushed a commit that referenced this issue Feb 27, 2023
Because the records which was deleted is not filtered in fill_row().
konghaiya pushed a commit to konghaiya/stonedb that referenced this issue Mar 7, 2023
…neatom#1199)

Because the records which was deleted is not filtered in fill_row().
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-bug Something isn't working B-DDL DDL related issues B-master-replica master/replica sync, replay B-storage data type, data storage, insert,update,delete, transactions prio: high High priority
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants