-
Notifications
You must be signed in to change notification settings - Fork 17
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
Remove SET NAMES usage which is no-op in SingleStore #33
base: main
Are you sure you want to change the base?
Conversation
0513ee9
to
ad9c98a
Compare
ad9c98a
to
58f9436
Compare
singlestoredb/mysql/connection.py
Outdated
Update Connection.encoding based on charset. | ||
|
||
If charset/collection are being set to utf8mb4, the corresponding global | ||
setting must be also utf8mb4. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm just wondering about this comment, this means, that the user should change it globally manually, before calling this function, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've updated the comment, please check.
We also need @kesmit13 opinion on this behavior. Maybe we should catch the error and print a warning instead, but ignoring it could lead to weird errors I guess - e.g when the user sets charset=utf8mb4
in connect()
, and then tries to write 4-byte symbols to utf8(mb3) tables
58f9436
to
756d21c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this change work in SingleStoreDB before 8.7? If not, we need to put in some sort of conditional to only do this change for that version. We can't break compatibility with older server versions.
No description provided.