Django ignores an application if it's trying to import a module that doesn't exist
|Reported by:||rynoinstereo||Owned by:||nobody|
|Component:||Database layer (models, ORM)||Version:||1.0|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
First off, I'm a brand new Django user so apologies if I don't make myself clear.
Just had a weird thing happen where I could not for the life of me, figure out why Django was saying all my Models were valid, yet when running manage.py validate and then syncdb, it would not create the tables for my newly created application.
The problem turned out to be that I was trying to include a model from one of my other applications ina the project but I had the name of the model wrong.
For some reason, this caused Django to completely ignore the model file for my newly created application, instead of reporting this as an error?
Change History (2)
comment:1 Changed 7 years ago by russellm
- Component changed from Testing framework to Database layer (models, ORM)
- milestone 1.1 deleted
- Needs documentation unset
- Needs tests unset
- Patch needs improvement unset
- Triage Stage changed from Unreviewed to Accepted