Hi, I think the concept of inherits is buggy as each time we try to use it on large scale (cf. expense module [1]) it fails because of the complexity and the impossibility to get a generic behavior that fits all the needs. So as a result, it is almost never used:
- calendar, calendar_todo:
But only for dev ease, it could be fixed with a Python inherit.
- carrier:
The usage is just a fallback and it could be dropped.
- company:
Idem as carrier and it could even perhaps improve the
understanding.
- project (work):
Could be changed with some function fields and perhaps it could
be smarter by not creating work for project not available on
timesheet.
- product:
Could be changed with a one2many on template to product with
default form view (like address on party).
And with some function field like the *_used ones.
- action:
This is technical and could be fixed in the code.
So I propose to simply drop it. I think the code of ModelSQL will be
much more simple if we drop all the contortions done to manage the
_inherits.
By the way, my last issue about _inherits is that the ir.rule of parent
object doesn't apply on the inherited which lead to a access right
error.
[1] http://codereview.tryton.org/178006
--
Cédric Krier
B2CK SPRL
Rue de Rotterdam, 4
4000 Liège
Belgium
Tel: +32 472 54 46 59
Email/Jabber: cedric.kr...@b2ck.com
Website: http://www.b2ck.com/
pgpFV9CStaAHP.pgp
Description: PGP signature
