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
mysql 8.0 fix likely breaks on case insensitive #4361
Comments
Michael Bayer (@zzzeek) wrote: if lower_case_table_names is zero, this is legal:
so we cant unconditionally lower case everything. we have to check that flag |
Michael Bayer (@zzzeek) wrote: well it doesn't reproduce with lower_case_table_names=1 because everything is lower case everywhere. I can't test with 2 beacuse I don't have a mac. |
Michael Bayer (@zzzeek) wrote: yeah im not finding any way to see what this really is, comparison of strings, etc. i need info from the user. |
Michael Bayer (@zzzeek) wrote: it breaks on lower_case_table_names=2 only because information_schema.columns preserves the original case of the schema name and tablename but SHOW CREATE TABLE does not, so the lookup fails. |
Michael Bayer (@zzzeek) wrote: https://gerrit.sqlalchemy.org/#/q/I748549bc4c27fad6394593f8ec93fc22bfd01f6c |
Michael Bayer (@zzzeek) wrote: Use case insensitive matching on lower_case_table_names=1,2 Fixed regression caused by 🎫 Fixes: #4361 → af159c5 |
Changes by Michael Bayer (@zzzeek):
|
Michael Bayer (@zzzeek) wrote: Use case insensitive matching on lower_case_table_names=1,2 Fixed regression caused by 🎫 Fixes: #4361 → 7f1294c |
Migrated issue, originally created by Michael Bayer (@zzzeek)
e.g. #4344, we have this:
if table names/schema are stored in lower case that will fail. user reporting this stack trace:
working on reproducing with an 8.0 with lower_case_table_names set to 1
release immediately upon fix
The text was updated successfully, but these errors were encountered: