What's a good way to handle orders?
What's a good way to handle orders?
- Subject: What's a good way to handle orders?
- From: Kevin Windham <email@hidden>
- Date: Sun, 6 Jan 2008 17:10:33 -0600
I have an app that will take orders. I didn't fully consider the
consequences of inserting the orders directly into the DB. Now I've
run into the situation where an order gets created and then someone
decides to simply close their browser before completing payment. Now
I have a "bad" order in the system.
My initial thought for dealing with this was simply to not insert the
order and associated lineitems into the db context until after the
process is complete. The problem with this is that it violates one of
the rules I've read about. That is, that you should insert objects
into the context before any manipulation of those objects.
Does anyone have an elegant solution for this, or should I simply
create some dummy objects and then clone them into new objects that I
insert into the DB immediately on creation?
Thanks,
Kevin
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden