#35575: Add support for constraint validation on GeneratedFields
-------------------------------------+-------------------------------------
Reporter: Mark Gensler | Owner: Mark
| Gensler
Type: New feature | Status: assigned
Component: Database layer | Version: 5.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: generatedfield | Triage Stage: Accepted
uniqueconstraint checkconstraint |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mark Gensler):
Replying to [comment:4 Sarah Boyce]:
>
> My gut says option 1
Yes, that seems the simpler approach which directly addresses this problem
and no more. Also from the definition of a `GeneratedField` in the docs:
> A field that is always computed based on other fields in the model. This
field is managed and updated by the database itself.
I'll work on option 1.
--
Ticket URL: <https://code.djangoproject.com/ticket/35575#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701907a5d60f7-b0352e95-2970-4f00-9293-2cc9b6c89845-000000%40eu-central-1.amazonses.com.
