On 27/06/12 19:36 +0200, Udo Spallek wrote: > Mon, 25 Jun 2012 13:10:16 +0200 > Cédric Krier <[email protected]>: > > On 25/06/12 11:16 +0200, Udo Spallek wrote: > > > But I do not understand, why stock.lot.type is connected to > > > location.type instead of the more explicit locations? > > Because we don't have a SelectionMulti fields. > I don't understand. Why we would need such a field and how will it > be used and how does it looks like?
Because the stock.lot.type are just a copy of the location type. But it was needed to store them in a table to allow multi-selection; > > Also we don't want to have to add every new location created to the > > configuration. > What is the problem with this? It doesn't scale if you have thousand of locations. > For me stock.lot.type model looks very restrictive and hard to > extend. I don't see why. For now it follow the same concept as the location. After that it is still possible to extend it by overriding Product.lot_is_required -- Cédric Krier B2CK SPRL Rue de Rotterdam, 4 4000 Liège Belgium Tel: +32 472 54 46 59 Email/Jabber: [email protected] Website: http://www.b2ck.com/
pgptBxjElCNVX.pgp
Description: PGP signature
