#2225: 'manage.py sql ...' gets confused when using tables from separate apps
-------------------------------------+-------------------------------------
Reporter: Lucas Hazel | Owner:
Type: defect | glassresistor
Component: Database layer | Status: closed
(models, ORM) | Version: master
Severity: minor | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by aaugustin):
* status: new => closed
* resolution: => fixed
Comment:
I've looked at the patches proposed to fix this ticket. They are not
needed after the app-loading refactor. See
6b172a6d6dcfe88be4dc0e5052707a756c1c830c and follow-up commits that
touched `django/core/management/__init__.py`.
If you're still seeing this problem, please check that it happens with
Django 1.7 (RC3 at this time) and open a new ticket -- that will be more
convenient than reopening a 4 years old ticket. Thanks!
--
Ticket URL: <https://code.djangoproject.com/ticket/2225#comment:12>
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/069.b76d4d9415da9ffde16aed4574443052%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
