#23459: not faking 0001_initial migration
----------------------------+--------------------------------------
Reporter: brian | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 1.7
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+--------------------------------------
Comment (by brian):
Hello,
Just noticed I hadn't replied to this for some time.
I would suggest that some sort of verbose/debugging output would be very
helpful. So you can see why Django isn't faking the migration.
e.g. "Not faking migration as expected table XYZ does not exist."
So it is possible to find out exactly what is going wrong without
resorting to hacking Django, as I previously did.
(For me it is most likely undetected errors in south migrations that only
occur under limited conditions that actually cause this)
Thanks
--
Ticket URL: <https://code.djangoproject.com/ticket/23459#comment:7>
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/063.9e55fc781388bf2f36d96a1de698f869%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
