Order integrity

[Marcos Passos]

Hello,

Currently, if a new order is created and the product is updated, this action is reflected in the order. For example: if I create a "potato" product, buy it and after update the product to tomato, the order shows I've bought tomatoes and not potatoes. The same occurs with the product relationships (attributes, options, etc).

What are you thinking about it to keep the order integrity?

Kind regards,

Marcos

[Paweł Jędrzejewski]

Yes, this is incorrect of course. My idea is quite simple, we'll store the relation to product, but save the itemName separately, which will hold the name of product from the time of ordering. Sounds reasonable?

[Marcos Passos]

Yes, but not solves at all. The same occurs with attributes, variants, options, etc. I suggest versioning (audit), saving the revision.

This project seems promissing.

What you think about?

Thanks,

Marcos

2012/6/28 Paweł Jędrzejewski <pm.jedr...@gmail.com>

[Paweł Jędrzejewski]

Yes it's interesting, I'll have a deeper look, I plan to talk to CMF guys, maybe we can use some of their stuff for versioning products.

[Marcos Passos]

Hello Pawel,

Maybe, ODM is a good solution in this case, once this data must never be updated. So, you can have a object Order, with all dependence without worry with a lot of "duplicated" tables.

Kind regards,

Marcos