#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 |
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"1690b92b0d53e625ef6623a317149013725015af"]:
{{{
#!CommitTicketReference repository=""
revision="1690b92b0d53e625ef6623a317149013725015af"
[1.7.x] Fixed #23987 -- Made SQLite SchemaEditor always use
effective_default().
Backport of 089047331d972c0ee58d13476fc54f2118bf1359 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23987#comment:6>
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.f13299d63f8dfdddcae40c7f46949157%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
