Validating model.CheckConstraints #9648
Replies: 1 comment 3 replies
-
|
I think this feature was added to Django a few versions back but that arrived at the time when DRF development slowed down, so support wasn't added until recently. There is currently partial support for it and some improvements were recently contributed, but some are unreleased:
|
Beta Was this translation helpful? Give feedback.
-
|
I specifically mean check constraints which are not checked. The problem is database integrity errors occur if check constraints are not handled during development and inside serializer. I am pleased and eager to contribute to this by developing support for check constraint handling inside serializer. |
Beta Was this translation helpful? Give feedback.
-
Anything that is in new django versions but not fully supported in DRF are high prority for us. so you can start working on missing django features in DRF. because those are needed for compatibility issues. ping me with a draft PR and here is a somewhat related issue #7173 |
Beta Was this translation helpful? Give feedback.
-
|
Ok. Thanks a lot. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
As far as I am concerned, DRF does not automatically support checking for database constraints defined in
model._meta.constrainstwhen it comes to serializer-level validation. Is there any reason why not?I am really determined to create a PR for this feature, but realized that DRF doesn't accept any new feature:
Why is that?
Beta Was this translation helpful? Give feedback.
All reactions