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

Use UniqueConstraint objects instead of unique_together #1434

Open
mikkonie opened this issue Jun 18, 2024 · 0 comments
Open

Use UniqueConstraint objects instead of unique_together #1434

mikkonie opened this issue Jun 18, 2024 · 0 comments
Labels
internal Changes invisible to the user or APIs (e.g. refactoring and optimization)

Comments

@mikkonie
Copy link
Collaborator

Django documentation hints that unique_together will be deprecated at some point in the future. Instead, we should use constraints and UniqueConstraint objects as documented here. The same also goes for SODAR et al.

Not urgent in any way, but I opened an issue as a reminder. If we do some kind of general model overhaul (e.g. fixing those __str__() and __repr__() definitions which are all over the place), this could be done at the same time.

@mikkonie mikkonie added the internal Changes invisible to the user or APIs (e.g. refactoring and optimization) label Jun 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
internal Changes invisible to the user or APIs (e.g. refactoring and optimization)
Projects
None yet
Development

No branches or pull requests

1 participant