#26168: BooleanField is forced to be blank=True
-------------------------------------+-------------------------------------
Reporter: fengyehong | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: BooleanField | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timgraham):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
* type: Uncategorized => Cleanup/optimization
* stage: Unreviewed => Accepted
Comment:
See #22282 and #23130 for some related discussion. I'm not sure what the
proper resolution is, but I'll accept the ticket since this this has come
up several time. We can at least document the reasons for this if it can't
be changed for backwards compatibility reasons.
--
Ticket URL: <https://code.djangoproject.com/ticket/26168#comment:1>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.bd99d1864b6b777d5ac84b046b26c4be%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
