#33408: Adding nullable OneToOneField crashes on SQLite.
-------------------------------------+-------------------------------------
Reporter: Alan Crosswell | Owner: Mariusz
| Felisiak
Type: Bug | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: sqlite3 | 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:"30613d6a748fce18919ff8b0da166d9fda2ed9bc" 30613d6a]:
{{{
#!CommitTicketReference repository=""
revision="30613d6a748fce18919ff8b0da166d9fda2ed9bc"
Fixed #33408 -- Fixed adding nullable unique fields on SQLite.
Regression in 2f73e5406d54cb8945e187eff302a3a3373350be.
Thanks Alan Crosswell for the report.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/33408#comment:3>
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/063.46e06807a911c9ead4e9d65d7ca30d6f%40djangoproject.com.
