Opened 10 years ago

Closed 5 years ago

Last modified 5 years ago

#9998 closed Cleanup/optimization (wontfix)

Document side effects of importing uninstalled models

Reported by: James Bennett Owned by: nobody
Component: Documentation Version: 1.0
Severity: Normal Keywords: app-loading
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


If a model is in an application not listed in INSTALLED_APPS, but is imported by some piece of code that's nonetheless in use, weird behavior can ensue (up to and including other models receiving reverse relations and thus erroring on delete operations when they try to select or delete from a non-existent related table).

This should be documented a bit more clearly, to ensure people don't trip over it.

Change History (6)

comment:1 Changed 10 years ago by Brian Rosner

Triage Stage: UnreviewedAccepted

comment:2 Changed 8 years ago by Chris Beaven

Severity: Normal
Type: Cleanup/optimization

comment:3 Changed 7 years ago by Aymeric Augustin

UI/UX: unset

Change UI/UX from NULL to False.

comment:4 Changed 7 years ago by Aymeric Augustin

Easy pickings: unset

Change Easy pickings from NULL to False.

comment:5 Changed 5 years ago by Tim Graham

Resolution: wontfix
Status: newclosed

The ability to do this has been deprecated in Django 1.7 and will be disallowed in Django 1.9 -- some documentation has been added about that; see #21680. I'm going to close this ticket since it hasn't been touched in 5 years.

comment:6 Changed 5 years ago by Aymeric Augustin

Keywords: app-loading added
Note: See TracTickets for help on using tickets.
Back to Top