#36076: Raise a check error if null=False and default=None
-------------------------------------+-------------------------------------
Reporter: Csirmaz Bendegúz | Owner: (none)
Type: New feature | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls):
* resolution: => wontfix
* status: new => closed
Comment:
I'm not sure how we could do this, since requiring python-level defaults
on model fields would break the pattern of defaulting fields empty but
[https://docs.djangoproject.com/en/dev/ref/models/fields/#blank supplying
missing values] during validation.
More thorough discussion here:
https://groups.google.com/g/django-developers/c/GlYM25fdRnA/m/wAimd4QPAwAJ
Happy to discuss further on the forum where more folks can contribute
ideas.
--
Ticket URL: <https://code.djangoproject.com/ticket/36076#comment:3>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/010701944b50318d-6b2ee3bb-3ee2-4514-8ec9-a59a9671802f-000000%40eu-central-1.amazonses.com.
