-
-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
Fix unique together validator doesn't respect condition's fields #9360
base: master
Are you sure you want to change the base?
Conversation
else: | ||
queryset = model._default_manager.filter(constraint.condition) | ||
condition_fields = [ | ||
f[0].split("__")[0] for f in constraint.condition.children |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not sure how reliable this method of fields extraction
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I duobt that this will work when the condition uses a cross-reference between two fields like: Q(first_field__gte=F('second_field'))
, however I dunno if an unique constraint like that makes sense.
I would like to see also a more complex condition like Q(fielda__isnull=True) | Q(fieldb=False)
to be addressed by this validator.
@kalekseev - Could you talk me through this? My understanding is that it's resolving an issue in #7438, is that correct? |
UPDATE: Yes, this pr is supposed to fix the initial implementation of UniqueConstraint support but at the moment it doesn't work. The problem is that DRF doesn't check if fields in data match the unique constraint condition or not, so for example constraint is:
we have record in db that should be unique
The data below should be valid because it has
but this should fail
|
fcc7c8d
to
472a323
Compare
fixes #9358