Well, that's an interesting point. I'd do 1 history table then maybe add a Type column so you can differentiate between the types of changes. You can then group the changes by date/time and type so you can see all customer changes for an order at 1:30 on 6/26/2006. Either way it will take some good queries and a good interface to showcase the changes properly.
On 6/25/06, Mike Little <[EMAIL PROTECTED]> wrote: > > ok a history table sounds good as i think we will need to check the > history of orders reasonably frequently. > > current my orders consist of the following tables... > > orders (the customer info, currency etc.) > orders_products (the products, price, qty) > orders_products_attributes (the options selected for each product) > > am i better to combine these for a history table or should i have 3 > history tables as above? in fact would i not need the customer info to be > duplicated? > > the attributes get a little trick as one product can have up to 4 rows in > the attributes table. > > mike > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:244771 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
