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
We've noticed that starting from 1.7.0+ releases the useUnicode and characterEncoding JDBC params in the JDBC URL are being ignored while executing TC_INITSCRIPT. Probably, other params are being ignored as well. As a result, if we have some, for example, russian symbols in the init SQL file, they are passed to the MySQL as a '?' signs, while on the 1.6.0 version it's not the case. Can you suggest what's the problem, is it a bug indeed?
Thanks!
The text was updated successfully, but these errors were encountered:
Hi @dmart28 - thanks for reporting and for the PR, and sorry for taking time to follow up. I wonder if this might be resolved by the much bigger refactoring within #617.
In any case, please could you show us a failing test that we could use to check?
Hi @rnorth - I've added a test to my PR which will fail without such fix. I've also checked #617 code and it doesn't seem to me that this issue is resolved here.
Hi!
We've noticed that starting from 1.7.0+ releases the
useUnicode
andcharacterEncoding
JDBC params in the JDBC URL are being ignored while executing TC_INITSCRIPT. Probably, other params are being ignored as well. As a result, if we have some, for example, russian symbols in the init SQL file, they are passed to the MySQL as a '?' signs, while on the 1.6.0 version it's not the case. Can you suggest what's the problem, is it a bug indeed?Thanks!
The text was updated successfully, but these errors were encountered: