#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
-------------------------------------+-------------------------------------

Comment (by jonashaag):

 There's an outdated patch in #23130, which I still think is the best
 solution to this problem. Somehow, I've never gotten around to finishing
 the patch, but I think it should take no more than an hour of time to get
 it up to date and pass the test suite.

--
Ticket URL: <https://code.djangoproject.com/ticket/26168#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 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/068.e062912163eec037e7987edd135e7bc8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to