#23987: sqlite backend don't always use effective_default
-------------------------------------+-------------------------------------
Reporter: coldmind | Owner: coldmind
Type: Bug | Status: closed
Component: Database layer | Version: master
(models, ORM) | Resolution: fixed
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"089047331d972c0ee58d13476fc54f2118bf1359"]:
{{{
#!CommitTicketReference repository=""
revision="089047331d972c0ee58d13476fc54f2118bf1359"
Fixed #23987 -- Made SQLite SchemaEditor always use effective_default().
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23987#comment:5>
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/066.15a7d3f5221e71c8e6a5dd49d0a01116%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
