DBAL 4 MySQL COLLATION 'utf8_bin' is not valid for CHARACTER SET 'utf8mb4'" at

[alexander-schranz]

DBAL 4 MySQL COLLATION 'utf8_bin' is not valid for CHARACTER SET 'utf8mb4'" at

[derrabus]

Can you try to isolate the problem a bit further? I'm not familiar with the codebase of that library.

[alexander-schranz]

Looks the error is unrelated to dbal. Atleast the utf8_bin coming from here not from dbal default definitions: https://github.com/jackalope/jackalope-doctrine-dbal/blob/607ff5d81c81b9cc0db7194e1a770d10b24203f5/src/Jackalope/Transport/DoctrineDBAL/Client.php#L381-L391

[alexander-schranz]

@derrabus the unexpected behaviour seems to be that we not longer know what encoding the database is using. before it always was utf8 in doctrine/dbal 3, defined here as a default:

dbal/src/Platforms/AbstractMySQLPlatform.php

Line 581 in 79ea9d6

$options['charset'] = 'utf8';

.

And it seems doctrine/dbal 4 not longer defines a default charset, and so it uses whatever the server defined as default charset, which did end in the unexpected behaviour as our logic is build currently ontop that if now charset defined it is utf8.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.