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
Django documentation hints thatunique_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.
The text was updated successfully, but these errors were encountered:
mikkonie
added
the
internal
Changes invisible to the user or APIs (e.g. refactoring and optimization)
label
Jun 18, 2024
Django documentation hints that
unique_together
will be deprecated at some point in the future. Instead, we should useconstraints
andUniqueConstraint
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.The text was updated successfully, but these errors were encountered: