Review: Needs Information Hi there. I noticed that this is not the implementation Maxime suggested. We are creating three with basically the same data fields (as Maxime predicted). >From an OO design and database normalization standpoint, this doesn't look good I'm sorry if changing my mind causes extra work, but I can see that Maxime was right.
If the one2many with domains is too difficult to implement (?), you could try subclasses: - create a "hr.curriculum" base class with all the common fields - make "hr.experience", "hr.academic", "hr.certification" inherit from "hr.curriculum" -- https://code.launchpad.net/~savoirfairelinux-openerp/openerp-hr/7.0-experience/+merge/195315 Your team Savoir-faire Linux' OpenERP is subscribed to branch lp:~savoirfairelinux-openerp/openerp-hr/7.0-experience. -- Mailing list: https://launchpad.net/~savoirfairelinux-openerp Post to : [email protected] Unsubscribe : https://launchpad.net/~savoirfairelinux-openerp More help : https://help.launchpad.net/ListHelp
