openerp-expert-production team mailing list archive

[Raphael Valyi <rvalyi@xxxxxxxxx>]

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