#24059: app_label not handled when set to the same project name in all the
django
app
----------------------------+--------------------------------------
Reporter: foxmask | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 1.7
Severity: Normal | Resolution: invalid
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 foxmask):
Replying to [comment:4 shaib]:
> In the second paragraph in my previous comment I explained that once you
set the model's app_label, Django treats it as if it belonged to the other
app. Again: Your model with `app_label = 'foobar'` belongs to the `foobar`
app, and the fact that it is defined in `foxmask/models.py` does not
matter.
>
> If this is still not clear to you, as I said, please use Django's
support channels.
I tested with db_table and it's ok. Now I have another problem
(OperationalError: no such table: xxx) , but with this current test case,
the problem I have in production, is not here. So thanks at least for
showing the path to the solution.
--
Ticket URL: <https://code.djangoproject.com/ticket/24059#comment:5>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.2d1b570521d6f0cabb72ea7b76088f53%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
