I have a situation where I have following relationship in the database:
- orders
- order_line_items is a child of orders
- order_line_item_options is a child of order_line_items
When I create a new order, the following happens:
1) new orders records
2) Add a line item to the order, which adds a new record to
order_line_item and a few records to order_line_item_options
3) Add another line item to the order
When 3 occurs, we haven't saved anything yet.
What I am seeing is when number 3 happens, the order_line_item bizobj
moves it's pointer to the new record, the order_line_item_options
bizobj requeries because it is a child of the order_line_item bizobj,
and the new records I added for the first order_line_item are erased
by the requery.
Now, should I be doing it this way? If so, then we should probably be
preserving the sub-child records. If not, what is the best way to
approach it? I can store them temporarily and create them after I save
the order and order_line_items records. The problem goes away if I
save the order first because I can save the order line items and their
options as need be, but it doesn't make sense to force the user down
that path for this data.
Regards,
Nate
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message:
http://leafe.com/archives/byMID/[email protected]
