Aurora (MySQL) Specified key was too long

[Nemo64]

Bug Report

Q	A
BC Break	no
Version	2.10.1

Summary

I use Amazons Aurora (Serverless) with MySQL compatibility. It doesn't seem to be 100% compatible since indexes aren't automatically truncated. I used the AuditBundle and it creates indexes using dbal. An example is this INDEX object_id_e06395edc291d0719bee26fd39a32e8a_idx (object_id).

Current behaviour

MySQL (5.6) automatically converts an index
like this: INDEX object_id_e06395edc291d0719bee26fd39a32e8a_idx (object_id)
to this INDEX object_id_e06395edc291d0719bee26fd39a32e8a_idx (object_id(191)).

Aurora doesn't. Instead I get an Specified key was too long; max key length is 767 bytes.

Expected behaviour

It should be possible to add the Sub_part to the create schema directly when the encoding is known. This will have no effect to existing schemas but allows to easily use Aurora instead of MySQL.

Current Workaround

I use migrations and one can simply add the Sub_part manually.

[Nemo64]

I noticed that this isn't an aurora problem but a mysql strict mode problem which is related to #3419 .

[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.