#15519: Custom SQL location
-------------------------------------+-------------------------------------
Reporter: vzima | Owner: nobody
Type: Bug | Status: new
Milestone: | Component: Core (Management
Version: 1.2 | commands)
Resolution: | Severity: Normal
Triage Stage: Accepted | Keywords:
Needs documentation: 1 | Has patch: 0
Patch needs improvement: 0 | Needs tests: 1
-------------------------------------+-------------------------------------
Comment (by vzima):
Replying to [comment:2 jacob]:
> This is potentially backwards-incompatible, sadly -- if people have SQL
in the (previously-incorrect) location it'll silently stop working. Not
sure what the best approach here is, but we probably have to look in both
places now.
This kind of backwards incompatible change was already done with fixtures
location, but it does not mean it needs to be done the same way. Keep both
places and mark old one as deprecated seems reasonable.
I can update patch if necessary.
--
Ticket URL: <http://code.djangoproject.com/ticket/15519#comment:3>
Django <http://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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
