Skip to content
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

Fixes MySQL distinction of 3 or 4byte UTF encoding. #55

Closed
wants to merge 1 commit into from

Conversation

sigysmund
Copy link

MySQL error: 1071 Specified key was too long; max key length is 767 bytes

The FIX had already been given as previous pull-request, but to my taste:
I did't want to use it, that's why I purpose an other possible FIX for the utf8 vs. utf8mb configs.

It solves issue #7

MySQL error: 1071 Specified key was too long; max key length is 767 bytes
@symfony-bot

This comment has been minimized.

@symfony-bot symfony-bot bot closed this Apr 16, 2020
@fabpot fabpot reopened this Apr 17, 2020
@nicolas-grekas nicolas-grekas changed the base branch from master to main November 19, 2020 12:29
@derrabus
Copy link
Member

This PR is not relevant for MySQL 5.7/8.0 anymore, is it?

@@ -33,6 +42,17 @@ public function __construct(array $options, Connection $connection = null)
{
$schemaConfig = null === $connection ? null : $connection->getSchemaManager()->createSchemaConfig();

$params = $connection->getParams();
if(array_key_exists('charset2', $params)) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why chartset2 ?

@derrabus derrabus closed this Jan 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants