Hi Eric, I did a quick scan of our code that could depend on that and at first glance I would see no issue with cost_method becoming a property.
Regards, -sbi On Fri, Jun 20, 2014 at 2:13 AM, Eric Caudal <[email protected]> wrote: > Hi, > Currently Odoo 7 doesnot handle properly 2 type of costing for separate > companies inside the same instance (average cost for company A and standard > cost for company B for example). > > We are using the product_price_history module for multi-company price > logging: would it be a good idea to change the cost_method to property > field within this module? > > What would be the impact on performance? > What would be the alternative? > -- > > Eric Caudal*CEO* > --*Elico Corporation, Shanghai branch > Odoo Premium Certified Training Partner > *Cell: + 86 186 2136 1670 > Office: + 86 21 6211 8017/27/37 > Skype: [email protected]http://www.elico-corp.com > > *Elico Corp is best Partner Odoo 2014 for Asia-Pacific* > *Remember: with version 8, OpenERP becomes Odoo!* > [image: Elico Corp] [image: Odoo Silver Partner] > > _______________________________________________ > Mailing list: https://launchpad.net/~openerp-community > Post to : [email protected] > Unsubscribe : https://launchpad.net/~openerp-community > More help : https://help.launchpad.net/ListHelp > >
_______________________________________________ Mailing list: https://launchpad.net/~openerp-community Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
