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

UNIQUE_REG_ID setting doesn't work with MySQL #577

Closed
xzander opened this issue Jun 4, 2020 · 2 comments
Closed

UNIQUE_REG_ID setting doesn't work with MySQL #577

xzander opened this issue Jun 4, 2020 · 2 comments

Comments

@xzander
Copy link

xzander commented Jun 4, 2020

If I set UNIQUE_REG_ID to True and then run migration 0007_uniquesetting.py, I get an error MySQLdb._exceptions.OperationalError: (1170, "BLOB/TEXT column 'registration_id' used in key specification without a key length"). Django won't fix it according to https://code.djangoproject.com/ticket/2495. And there is a note about the issue in docs https://docs.djangoproject.com/en/2.2/ref/databases/#textfield-limitations

registration_id is TextField in GCMDevice, WNSDevice and WebPushDevice

@jlbeltran
Copy link

Any clue about this?

@jamaalscarlett
Copy link
Member

Given that this is a known Django issue, I'm not sure what we can do other than update the docs to detail this issue in the docs.

jamaalscarlett added a commit that referenced this issue Apr 29, 2024
Adds note to explain: #577
jamaalscarlett added a commit that referenced this issue Jun 3, 2024
Adds note to explain: #577
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants