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
Heyo. I'd like to point out that running tests with MySQL is not working because of the unique=True of registration_id. I know this issue was "fixed" in the migrations. But running migrations while testing is not an option for us (> 1000 migrations). So we deactivate migrations via https://docs.djangoproject.com/en/5.0/ref/settings/#migrate. And that leads to
django.db.utils.OperationalError: (1170, "BLOB/TEXT column 'registration_id' used in key specification without a key length")
Can we therefore set unique=False in the model as well, if the db is mysql? Thx
The text was updated successfully, but these errors were encountered:
tuky
changed the title
OperationalError: "max key length is 3072 bytes" when running tests with MySQL
OperationalError: "max key length is 3072 bytes" when running tests w/ MySQL w/o migrations
May 15, 2024
Heyo. I'd like to point out that running tests with MySQL is not working because of the
unique=True
ofregistration_id
. I know this issue was "fixed" in the migrations. But running migrations while testing is not an option for us (> 1000 migrations). So we deactivate migrations via https://docs.djangoproject.com/en/5.0/ref/settings/#migrate. And that leads toCan we therefore set
unique=False
in the model as well, if the db ismysql
? ThxThe text was updated successfully, but these errors were encountered: