model is declared but cannot be loaded!
Bug #955180 reported by
Dimitri John Ledkov (ex-credativ)
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenUpgrade Tools - obsolete |
New
|
Undecided
|
Unassigned | ||
Bug Description
I get a lot of warnings of model is declared but cannot be loaded.
Some of them may have data.
Most of them are osv.memory wizards.
Maybe the osv.memory wizard models which are removed should be dropped from ir_model on upgrade?
Related branches
lp:~therp-nl/openupgrade-tools/7.0-add-database_cleanup
- Pedro Manuel Baeza: Needs Fixing (code review and test)
-
Diff: 1054 lines (+972/-0)15 files modifieddatabase_cleanup/__init__.py (+1/-0)
database_cleanup/__openerp__.py (+55/-0)
database_cleanup/model/__init__.py (+6/-0)
database_cleanup/model/purge_columns.py (+154/-0)
database_cleanup/model/purge_data.py (+106/-0)
database_cleanup/model/purge_models.py (+127/-0)
database_cleanup/model/purge_modules.py (+91/-0)
database_cleanup/model/purge_tables.py (+138/-0)
database_cleanup/model/purge_wizard.py (+64/-0)
database_cleanup/view/menu.xml (+48/-0)
database_cleanup/view/purge_columns.xml (+37/-0)
database_cleanup/view/purge_data.xml (+37/-0)
database_cleanup/view/purge_models.xml (+36/-0)
database_cleanup/view/purge_modules.xml (+36/-0)
database_cleanup/view/purge_tables.xml (+36/-0)
Revision history for this message
| Stefan Rijnhart (Opener) (stefan-opener) wrote | #1 |
| Changed in openupgrade-server: | |
| importance: | Undecided → Low |
| status: | New → Confirmed |
| no longer affects: | openupgrade-server |
To post a comment you must log in.
Yes, dropping the obsolete memory models should be safe now that upgrading requires only a single run. Any trouble that may cause should be handled by the scripts.
Maybe try and remove regular models as well. I can see this cramped model namespace clogging up over time. Prefix tables with x_openupgrade_ after removing triggers.