-
-
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: ERROR 1010 (HY000): Error dropping database #662
Labels
Milestone
Comments
trace log:
error returned from |
For
When get file extensions from each plugin, we'll get extensions like |
In stonedb 5.7, it use
but in 8.0, changed to a variable setted in
|
hustjieke
added a commit
to hustjieke/stonedb-8.0.30-upgrade
that referenced
this issue
Oct 11, 2022
…ase error stoneatom#662 [summary] When drop database, mysqld cannot find tianmu file extension and drop failed. 1. change all `rcbase_hton` to `tianmu_hton`, just like innodb, myisam, csv ... does. 2. rm function bas_ext(), it used in 5.7, but removed in 8.0 and changed to a variable instead. 3. Add tianmu file extension to tianmu_hton->file_extensions.
15 tasks
mergify bot
pushed a commit
that referenced
this issue
Oct 12, 2022
…ase error #662 [summary] When drop database, mysqld cannot find tianmu file extension and drop failed. 1. change all `rcbase_hton` to `tianmu_hton`, just like innodb, myisam, csv ... does. 2. rm function bas_ext(), it used in 5.7, but removed in 8.0 and changed to a variable instead. 3. Add tianmu file extension to tianmu_hton->file_extensions.
Repository owner
moved this from In Progress
to Done
in StoneDB for MySQL 8.0
Oct 12, 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
If database has table, can not drop it:
Expected behavior
drop database success.
How To Reproduce
Environment
Are you interested in submitting a PR to solve the problem?
The text was updated successfully, but these errors were encountered: