-
-
Notifications
You must be signed in to change notification settings - Fork 141
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
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
Milestone
Comments
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().
14 tasks
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 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
Have you read the Contributing Guidelines on issues?
Please confirm if bug report does NOT exists already ?
Describe the problem
Expected behavior
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?
The text was updated successfully, but these errors were encountered: