Opened 12 years ago

Closed 11 years ago

Last modified 11 years ago

#20873 closed Bug (fixed)

Model options assumes incorrectly that model classes resides in models-module

Reported by: Jani Tiainen Owned by: nobody
Component: Database layer (models, ORM) Version: 1.5
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

Description

If you use splitted models, like having a models in submodules of models Model._meta.installed will get always false.

Models installed in app/models.py will get correctly Model._meta.installed flag set as a True.

Attachments (1)

django-20873.tar.gz​ (5.2 KB ) - added by Jani Tiainen 12 years ago.
Test case

Download all attachments as: .zip

Change History (4)

by Jani Tiainen, 12 years ago

Attachment: django-20873.tar.gz​ added

Test case

comment:1 by Ramiro Morales, 12 years ago

Triage Stage: Unreviewed → Accepted

See ​https://github.com/django/django/blob/07876cf02b6db453ca0397c29c225668872fa96d/django/db/models/options.py#L79

Thanks jtiai for the report and test case.

comment:2 by Claude Paroz, 11 years ago

Resolution: → fixed
Status: new → closed

Fixed by [7eea9bf30399e9a49fe164851c6132cd19a88e08]

comment:3 by Aymeric Augustin, 11 years ago

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