I'm trying to design a small webstore and running into some issues. I have an order that has multiple lines. If any of those lines change in quantity my stock entity should reflect that, so they should be wrapped in a transaction. But as an order can have multiple lines (referring to multiple stocks) and can has only one parent that won't work.
So I will create two entities for the order: Order OrderLine (parent: stock) But now I have a problem with the order/orderline group, as they need to be transactional too. So I was thinking, get rid of the order object and only have orderlines, but that doesn't solve anything because the orderlines will not be transactional with other orderlines they relate to. So the only thing I can still think of is making a store entity and make it the parent of orders and stocks like this: Store Stock (parent: store) Order (parent: store) But this will give me horrible performance as every stock or order can only be updated max 5 times a second (for being in the same entity group). Anyone got a better idea? - Koen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
