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
If MySQL's charset is utf8, SQLAlchemy's database connection url should set like following. mysql://foo:foo_password@localhost/bar_table?charset=utf8&use_unicode=0
Currently, database.py ignore url query string.
So, dataset can't handle multibyte correctly.
SQLAlchemy convert to multibyte char to ? automatically.
Yeah, overloading the URL query string to handle dataset arguments was probably a stupid move. I'll try and refactor to leave the non-specific bits of the query string intact. Thanks for pointing it out!
Hi. Thank you for create nice library.
I've got multibyte problem.
If MySQL's charset is utf8, SQLAlchemy's database connection url should set like following.
mysql://foo:foo_password@localhost/bar_table?charset=utf8&use_unicode=0
Currently,
database.py
ignore url query string.So,
dataset
can't handle multibyte correctly.SQLAlchemy convert to multibyte char to
?
automatically.Is there any reason to ignore url query?
IMHO
dataset
should not ignore url query for handling multibyte.Regards.
The text was updated successfully, but these errors were encountered: