openerp-expert-production team mailing list archive

[Leonardo Pistone <leonardo.pistone@xxxxxxxxxxxxxx>]

Thanks for the explanation Raphael.
Yes, I think that is the case. I made MP's for 6.1 and 7.0, the latter
includes a backport of base_custom_attributes

https://code.launchpad.net/~camptocamp/openerp-product-attributes/6.1-backport-lot-custom-attributes-lep/+merge/196538
https://code.launchpad.net/~camptocamp/openerp-product-attributes/7.0-adding-stock_production_lot_custom_attributes-lep/+merge/195950

Best,
L



On Mon, Nov 25, 2013 at 6:21 PM, Raphael Valyi <rvalyi@xxxxxxxxx> wrote:

> On Wed, Nov 20, 2013 at 6:29 AM, Leonardo Pistone <
> leonardo.pistone@xxxxxxxxxxxxxx> wrote:
>
>> Hi all
>>
>> I am developing a module that is all like product_custom_attributes (in
>> https://launchpad.net/openerp-product-attributes) and depends on
>> base_custom_attributes as well (module is in the same place). Difference
>> is, mine is for stock.production.lot.
>>
>> For uniformity with the other two modules, I suggest placing it also in
>> lp:openerp-product-attributes and calling it
>> production_lot_custom_attributes.
>>
>> Do you agree, any thoughts?
>>
>
>
> Hello Leonardo,
>
> often an attribute fits better as a standard extra SQL column created by
> an OpenERP field in an extension module. The reason we developed
> base_custom_attributes is because in e-commerce we have attributes that
> changes a lot, according to every collection of products, with possibly too
> many different attributes to fit in the same table with reasonable
> performance and ideally we don't want to require this to be coded in Python
> for every situation and every possible change. base_custom_attributes is
> also attractive if your attributes are sparsely filled.
> Are you sure you are in such a case? If yes, then yes go for it.
>
> Regards.
>
>
> --
> Raphaël Valyi
> Founder and consultant
> http://twitter.com/rvalyi <http://twitter.com/#!/rvalyi>
> +55 21 2516 2954
> www.akretion.com
>
>
>