#23130: BooleanField should not override 'blank' if choices are specified
-------------------------------------+-------------------------------------
Reporter: Jonas H. | Owner: (none)
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* owner: Tushar Bhatia => (none)
* status: assigned => new
Comment:
I've looked at this a little but much work remains. Here's my WIP
[https://github.com/django/django/pull/8467 PR] to allow `null=True` for
`BooleanField`. Most everywhere `NullBooleanField` is tested in Django's
test suite, a parallel test for `BooleanField(null=True)` should also be
added. I think there may also be some trickiness with regards to
migrations and changing the nullability of `BooleanField`. For example, on
Oracle, it requires adding or dropping
[https://github.com/django/django/blob/e86f4786a7f39b0ed833c0699addf0c27811d864/django/db/backends/oracle/base.py#L112
a check constraint]. I'm not planning to continue this in the immediate
future, so someone else can continue with my initial patch.
--
Ticket URL: <https://code.djangoproject.com/ticket/23130#comment:20>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.c15932aaf97e2c7aa02636bb865e863e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
