fix: dont run model unique constraint on ExamSerializer #265
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This serializer will fail to validate any 'update' operation once DRF 3.15 is pulled in. This endpoint is designed to validate the payload first than update or create objects as needed. The problem with this is the validator won't know we're updating an existing instance or creating a new one so it rejects anything that matches an existing exam row. This constraint isn't valuable on this endpoint anyway since if it already exists we're always going to update, it's impossible to create duplicates.
This was only working before due to encode/django-rest-framework#7173 which got fixed in 3.15.