You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A schema name that starts with an upper case character (MySchema) will be created fine and works for the most part, but
an edr cannot be generated (the regexp in edr.m searching for data tiers enforces lower case)
creates confusing errors for joins, because the search for foreignkeys in dj.Table returns duplicate entries and ultimately generates spurious error messages about duplicate fields that need to be projected out. These errors disappear after clear classes, but reappear on the second run of the same query;
@bartkrekelberg Good catch! Yes, this seems like a bug. It used to be that MySQL treated schema names as case-insensitive so we defaulted to lower-case but seems like that policy was not 100%.
Bug Report
Description
A schema name that starts with an upper case character (MySchema) will be created fine and works for the most part, but
Reproducibility
Include:
Expected Behavior
Probably the easiest fix is to enforce a lower-case letter at the start of a schema name when the schema is first created.
The text was updated successfully, but these errors were encountered: