#33133: NullBooleanField doesn't work in historical migrations.
-------------------------------------+-------------------------------------
Reporter: Mariusz Felisiak | Owner: Mariusz
| Felisiak
Type: Bug | Status: closed
Component: Database layer | Version: 4.0
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by GitHub <noreply@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"3b9fe906bf28d2e748ce4d9a1af5fbcd5df48946" 3b9fe906]:
{{{
#!CommitTicketReference repository=""
revision="3b9fe906bf28d2e748ce4d9a1af5fbcd5df48946"
Fixed #33133 -- Fixed handling NullBooleanField in historical migrations.
Regression in d992f4e3c29a81c956d3d616f0bc19701431b26e.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/33133#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 on the web visit
https://groups.google.com/d/msgid/django-updates/065.c5ec4b224634d97a9e6b8f4b32ca0398%40djangoproject.com.
