+1 for thanking you for all your comments By the sound of it, the main thing stopping someone from saving cart data in the database is the resource usage (bloated database, slow connection, bottleneck). I reckon this is best solved by improving: * connection to DB * writing smarter queries * indexes etc...
rather than trying to craete a temporary database system in the form of a session. A database will always be a better place to save data then a session. One thing you will have to do if course is to link the data in the database to a session. Otherwise, storing cart data in the database will require a user login / sign-up - which is unattractive from a usability perspective. On the other hand, an order saved to be DB can be retrieved from a different location if the user does save his / her order. Also, with orders saved in the database, it is easier to have several orders on the go at once (and switch between them), something that would be tricky to achieve with sessions. For some e-commerce situations this could be useful. Does anyone know how famous ecommerce systems do it (e.g. Magento)? Nicolaas -- NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected]
