Details
Description
I am working with 11.0.2 and (varios clients, one of them is ) MySQL.Data.MySQLConnector.
The new feature for multiple collations with NULL ID (MDEV-27009) broke the connector as you can see here:
I know the problem is in the connector internals, but how I can disable the new collations to make the connection connect until they will fix it ?
Thanks for a must-using product !
Attachments
Issue Links
- causes
-
MDEV-33531 Document new old mode NO_NULL_COLLATION_IDS
-
- Closed
-
- is caused by
-
MDEV-27009 Add UCA-14.0.0 collations
-
- Closed
-
- is duplicated by
-
MDEV-32816 Make "show collations" data not-nullable
-
- Closed
-
-
MDEV-32865 Get datas from Table
-
- Closed
-
- relates to
-
MDEV-24121 Recent MariaDB update appears to have introduced a DB connection issue for PHP < 7.3 (or anything using PDO)
-
- Closed
-
- links to
Hi I just published pre-pre-alpha version of package trying to fix this issue before fix in mariadb-server will be publicly available. You can try it and let me know if it helped.
NuGet: https://www.nuget.org/packages/Jf.MySql.Data.Collations/
Sources: https://github.com/jeffraska/Jf.MySql.Data.Collations/
The package is in "works on my computer" state. This means .NET framework 4.5, really old MySql.Data 6.9.7 library and latest MariaDB 10.11.4 currently available in Debian repository. So don't expect miracles.
It uses standard Command Interceptor functionality of MySql.Data library (https://dev.mysql.com/doc/connector-net/en/connector-net-interceptors.html) to alter all `SHOW COLLATION` queries and replacing it with `SHOW COLLATION WHERE id IS NOT NULL`.
Also the package have functionality to alter MySql.Data's internal charset mapping to allow reading utf8mb3 fields in pre 8.0.28 versions of MySql.Data .