#36286: if I specify `null=False, blank=False` in a `models.TextField`, django
should not generate a blank string for me
-------------------------------------+-------------------------------------
Reporter: bwo | Owner: (none)
Type: Bug | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Natalia Bidart):
* component: Uncategorized => Database layer (models, ORM)
* resolution: wontfix => invalid
* type: Uncategorized => Bug
* version: 5.1 => dev
Comment:
Thank you Clifford for the triage! I will just adjust the resolution,
since for tickets that are a user support request we usually close them as
`invalid`. We usually use `wontfix` for New Feature requests.
--
Ticket URL: <https://code.djangoproject.com/ticket/36286#comment:2>
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 visit
https://groups.google.com/d/msgid/django-updates/01070195f78e6d93-a3d22ef9-ce05-479b-a5ea-78ecb44f403a-000000%40eu-central-1.amazonses.com.
