#2225: 'manage.py sql ...' gets confused when using tables from separate apps
-------------------------------------+-------------------------------------
Reporter: Lucas Hazel | Owner:
Type: defect | glassresistor
Component: Database layer | Status: new
(models, ORM) | Version: master
Severity: minor | Resolution:
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 domonique.carter@…):
* status: closed => new
* ui_ux: => 0
* resolution: fixed =>
* easy: => 0
Comment:
Replying to [comment:10 russellm]:
> I'm pretty sure this problem doesn't exist anymore.
I am actually still getting the error from sqlall. I type in python
manage.py sqlall data user. data and user are both applications. One of
the models in user references a model in data. From my understanding of
the previous statements; syncdb actually just adds the alter statement to
the create statement. Is that a correct interpretation.
--
Ticket URL: <https://code.djangoproject.com/ticket/2225#comment:11>
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.bf6d2c197806200faf4c59a51e9fec2c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
