#27168: "LookupError: App 'xxxxx' doesn't have a 'xxxxx' model" with custom
table
name
----------------------------+--------------------------------------
Reporter: chagh | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.8
Severity: Normal | Resolution:
Keywords: migration | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+--------------------------------------
Comment (by timgraham):
I couldn't reproduce this on both master and Django 1.8.x. In both cases,
`model_name='MyModel'` worked after adding a custom `db_table`. Could you
provide a sample project that reproduces the issue?
--
Ticket URL: <https://code.djangoproject.com/ticket/27168#comment:2>
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.2259312b79aa106cd1e71db40f13be8c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
