-
-
Notifications
You must be signed in to change notification settings - Fork 625
registration_id unique constraint fails on PUT (Update) #270
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
Milestone
Comments
This appears to be a known issue with writable nested serializers encode/django-rest-framework#2403 |
jamaalscarlett
added a commit
to jamaalscarlett/django-push-notifications
that referenced
this issue
Jan 21, 2016
When the serializer is nested the unique validator on registration_id does not behave correctly. This is a known issue with DRF see: encode/django-rest-framework#2403 Added missing allow_null to device_id field Fixes jazzband#270
jamaalscarlett
added a commit
to jamaalscarlett/django-push-notifications
that referenced
this issue
Jan 21, 2016
When the serializer is nested the unique validator on registration_id does not behave correctly. This is a known issue with DRF see: encode/django-rest-framework#2403 Added missing allow_null to device_id field Fixes jazzband#270
jamaalscarlett
added a commit
to jamaalscarlett/django-push-notifications
that referenced
this issue
Jan 21, 2016
When the serializer is nested the unique validator on registration_id does not behave correctly. This is a known issue with DRF see: encode/django-rest-framework#2403 Added missing allow_null to device_id field Fixes jazzband#270
jamaalscarlett
added a commit
to jamaalscarlett/django-push-notifications
that referenced
this issue
Jan 22, 2016
When the serializer is nested the unique validator on registration_id does not behave correctly. This is a known issue with DRF see: encode/django-rest-framework#2403 Added missing allow_null to device_id field Fixes jazzband#270
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We use GCMDeviceSerializer as nested serializer
and it always fails validation when we try to update our Data object with message:
{"gcm_device":{"registration_id":["This field must be unique."]}}
It seems that following code executes on both create and update calls:
The text was updated successfully, but these errors were encountered: