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

Bug 988134: Drop the unique constraint on client_state. #123

Merged
merged 1 commit into from
May 30, 2018
Merged

Conversation

rfk
Copy link
Contributor

@rfk rfk commented May 28, 2018

This basically ports the changes from Bug 988134 over to the custom node-assignment backend used in this repo.

I didn't bother with creating a formal db migration, because the code should all still work for anyone with an existing install. But the constraint is unnecessary and removing it will fix #121 and similar issues.

@timakro any chance you could try this out and let me know if it works for you?

@timakro
Copy link

timakro commented May 29, 2018

This solves my issue. I created a new database and the tables where created successfully this time. Thanks!

@rfk
Copy link
Contributor Author

rfk commented May 30, 2018

Great! 👍

@rfk rfk merged commit 96e3b49 into master May 30, 2018
Mic92 pushed a commit to Mic92/syncserver that referenced this pull request Feb 23, 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.

Specified key was too long; max key length is 767 bytes
2 participants