Validation problem: `parent` isn't set for nested serializer's fields on the validation stage

Question

Validation problem: `parent` isn't set for nested serializer's fields on the validation stage

ruscoder opened this issue 7 years ago · 8 comments

I had found a problem on the validation stage when I used UniqueValidator for nested serializer's field.
I've found the root of the problem - parent isn't set on the validation stage.

Answer 1 · 2017-11-13T22:52:04.000Z

Same as #28

Answer 2 · 2017-11-16T22:00:45.000Z

I believe this fixes it: #29

Answer 3 · 2017-11-17T03:05:54.000Z

@cjroth #29 is connected to one-to-one relations only. This issue relates to the more common problem and only on the validation stage.

Answer 4 · 2017-12-04T04:24:25.000Z

http://www.django-rest-framework.org/api-guide/validators/#updating-nested-serializers

Answer 5 · 2018-08-17T09:43:56.000Z

Now we are working on a workaround for this issue

Answer 6 · 2018-08-23T10:05:24.000Z

There is an example how to get a workaround:
https://github.com/beda-software/drf-writable-nested#validation-problem-for-nested-serializers-with-unique-fields-on-update

Answer 7 · 2018-09-07T10:32:06.000Z

but DRF also proposes way to deal with bulk updates by explicitly including id field (as not read_only)
http://www.django-rest-framework.org/api-guide/serializers/#customizing-multiple-update

this way, one get instance from id

ps.: in my case I had custom kind of uniqueness validation (checked if objects not overlap), so I excluded current instance by id in my validation query.

Answer 8 · 2022-12-08T09:23:40.000Z

Would UniqueFieldsMixin move validations of unique_together as well?