lp://staging/~openerp-dev/openobject-server/6.0-bug-731487-xrg
- Get this branch:
- bzr branch lp://staging/~openerp-dev/openobject-server/6.0-bug-731487-xrg
Branch merges
- OpenERP buildbot (community): Approve
-
Diff: 62 lines (+40/-1)2 files modifiedbin/addons/base/ir/ir_model.py (+7/-1)
bin/osv/orm.py (+33/-0)
Related bugs
Bug #731487: [6.0] SERVER : Can not add a osv.memory field from the Openerp interface | Undecided | Fix Committed |
Related blueprints
Branch information
Recent revisions
- 3362. By xrg
-
ORM: let orm_memory models have custom fields [Bug: 731487]
This is a _feature_ patch.
Reported by: Sébastien BEAU @ akretion.comUntil now, creating custom fields in orm_memory objects (like x_foo)
was not really supported. The _columns of the model wouldn't be updated.
Introduce this functionality, and also fix renaming of the _columns for
them.Note, we still /don't/ support reading the new column of a record that
had been created before the column was added from the GUI. Since orm_memory
records are volatile, this functionality may be unnecessary. - 3357. By Jay Vora (Serpent Consulting Services)
-
[MERGE] Merged the branch for the fix of creation of x2many values.(ref: Case 4364)
- 3356. By Olivier Dony (Odoo)
-
[FIX] res_partner: extend default security rule to show partners from ancestors companies too
This rules is not suited for most OpenERP objects, but it works
well for partners and products as these records are usually
shared between companies, and all company-specific data (such as
acounting data is set as per-company properties). A partner or
product can thus be shared cleanly between companies.
This was already possible before by just removing the company
assigned to the partner, making it globally visible.
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp://staging/openobject-server