#35671: Clarify behavior for Field.null=False on string-based fields
-------------------------------------+-------------------------------------
Reporter: Clifford Gama | Owner: Clifford
Type: | Gama
Cleanup/optimization | Status: assigned
Component: Database layer | Version: 5.1
(models, ORM) |
Severity: Normal | Resolution:
Keywords: Field.null; | Triage Stage: Ready for
IntegrityError; | checkin
NotNullConstraint; Field.default |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce):
* summary: Document how to disallow blank values in Char/TextFields =>
Clarify behavior for Field.null=False on string-based fields
--
Ticket URL: <https://code.djangoproject.com/ticket/35671#comment:9>
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/010701916ab6ff53-bfc0bc4e-8604-43ff-a291-f913c2c3c6e6-000000%40eu-central-1.amazonses.com.
