Re: What's a good way to handle orders?
Re: What's a good way to handle orders?
- Subject: Re: What's a good way to handle orders?
- From: Kevin Windham <email@hidden>
- Date: Sun, 6 Jan 2008 17:27:26 -0600
On Jan 6, 2008, at 5:20 PM, James C. Lee wrote:
Kevin,
How about add a numeric column "status" to the Order table, with
values such
as:
0 = newly order
1 = got credit card info, ready for authorization
2 = authorization successful, ready to pack
3 = authorization failed
4 = packed, ready to charge credit card
5 = credit card charged
...
11 = paypal payment received
etc.
I thought about doing a status, but then I could still end up with
orders that are cluttering up the db for no good reason. A person
really on the fence could go in several times and create the same
order on different days before finally deciding to purchase. Then I
would have to go back and search out "bad" orders and clean it up.
I think it will be best to not have the order go into the db until
payment is made, just not sure what the best way to do that is. I'm
leaning toward duplicate objects and then clone the temp objects into
the freshly created db inserted objects upon payment.
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