-
-
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: delete from Multiple-Table, Failed to delete the data #663
Comments
konghaiya
added a commit
to konghaiya/stonedb
that referenced
this issue
Oct 18, 2022
)(stoneatom#678) Cause: At present, the primary key of the tianmu engine does not fully support delete and update statements. Temporary solution: Modify the execution plan of the SQL layer so that the delete and update statements do not follow the primary key logic
konghaiya
added a commit
to konghaiya/stonedb
that referenced
this issue
Oct 18, 2022
…toneatom#663)(stoneatom#678) Cause: At present, the primary key of the tianmu engine does not fully support delete and update statements. Temporary solution: Modify the execution plan of the SQL layer so that the delete and update statements do not follow the primary key logic
15 tasks
konghaiya
added a commit
to konghaiya/stonedb
that referenced
this issue
Oct 18, 2022
…toneatom#663)(stoneatom#678) Cause: At present, the primary key of the tianmu engine does not fully support delete and update statements. Temporary solution: Modify the execution plan of the SQL layer so that the delete and update statements do not follow the primary key logic
konghaiya
added a commit
to konghaiya/stonedb
that referenced
this issue
Oct 18, 2022
…toneatom#663)(stoneatom#678) Cause: At present, the primary key of the tianmu engine does not fully support delete and update statements. Temporary solution: Modify the execution plan of the SQL layer so that the delete and update statements do not follow the primary key logic
konghaiya
added a commit
to konghaiya/stonedb
that referenced
this issue
Oct 18, 2022
…toneatom#663)(stoneatom#678) Cause: At present, the primary key of the tianmu engine does not fully support delete and update statements. Temporary solution: Modify the execution plan of the SQL layer so that the delete and update statements do not follow the primary key logic
konghaiya
added a commit
to konghaiya/stonedb
that referenced
this issue
Oct 18, 2022
…toneatom#663)(stoneatom#678) Cause: At present, the primary key of the tianmu engine does not fully support delete and update statements. Temporary solution: Modify the execution plan of the SQL layer so that the delete and update statements do not follow the primary key logic
konghaiya
added a commit
to konghaiya/stonedb
that referenced
this issue
Oct 18, 2022
…toneatom#663)(stoneatom#678) Cause: At present, the primary key of the tianmu engine does not fully support delete and update statements. Temporary solution: Modify the execution plan of the SQL layer so that the delete and update statements do not follow the primary key logic
konghaiya
added a commit
to konghaiya/stonedb
that referenced
this issue
Oct 18, 2022
…toneatom#663)(stoneatom#678) Cause: At present, the primary key of the tianmu engine does not fully support delete and update statements. Temporary solution: Modify the execution plan of the SQL layer so that the delete and update statements do not follow the primary key logic
konghaiya
added a commit
to konghaiya/stonedb
that referenced
this issue
Oct 19, 2022
…toneatom#663)(stoneatom#678) Cause: At present, the primary key of the tianmu engine does not fully support delete and update statements. Temporary solution: Modify the execution plan of the SQL layer so that the delete and update statements do not follow the primary key logic
konghaiya
added a commit
to konghaiya/stonedb
that referenced
this issue
Oct 19, 2022
…toneatom#663)(stoneatom#678) Cause: At present, the primary key of the tianmu engine does not fully support delete and update statements. Temporary solution: Modify the execution plan of the SQL layer so that the delete and update statements do not follow the primary key logic
konghaiya
added a commit
to konghaiya/stonedb
that referenced
this issue
Oct 20, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Have you read the Contributing Guidelines on issues?
Please confirm if bug report does NOT exists already ?
Describe the problem
Failed to delete the data!
Expected behavior
How To Reproduce
Environment
ubuntu@ubuntu:~$ cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04.4 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.4 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
ubuntu@ubuntu:~$ /stonedb57/install/bin/mysqld --version
/stonedb57/install/bin/mysqld Ver 5.7.36_v1.0.1_beta_2-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: 208f79d
Last commit time: Date: Sat Sep 17 16:19:42 2022 +0800
Build time: Date: Fri Sep 23 14:14:27 CST 2022
Are you interested in submitting a PR to solve the problem?
The text was updated successfully, but these errors were encountered: