#35671: Clarify behavior for Field.null=False on string-based fields
-------------------------------------+-------------------------------------
Reporter: Clifford Gama | Owner: Clifford
Type: | Gama
Cleanup/optimization | Status: closed
Component: Database layer | Version: 5.1
(models, ORM) |
Severity: Normal | Resolution: fixed
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 <42296566+sarahboyce@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"ca1318988c68f623ab12ab4ddb04eabb8afe5a33" ca131898]:
{{{#!CommitTicketReference repository=""
revision="ca1318988c68f623ab12ab4ddb04eabb8afe5a33"
Fixed #35671 -- Clarified string-based fields behavior when null=False.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35671#comment:10>
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/010701916e67dbf9-1f1e4921-7bdd-4b5c-b9b3-abbe10dbc54a-000000%40eu-central-1.amazonses.com.
