every cart systems I have worked with , overriding php default session handler, and stored session data inside Relational DB.
I can think of 2 reasons why store session data in DB. 1. your cart needs to run on multiple servers. so you can have center / cluster DB server to handle your session data. 2. your cart needs to run on shared host which does not have enough space / permission to stored your session data in file system. a simple cart infor session contains following information: an user login id. a collection of items/products's id. whenever , a user logged in or check out, your have to store that cart infor session into table(s). On 15 July 2010 18:44, nicolaas <[email protected]> wrote: > Hi Folk > > Are there any arguments for or against the use of session for saving > cart information before committing it to a database (usually at the > moment of sale confirmation)? > > For: > * less database clutter > * faster? > > Against: > * more code > * less information on potential sales is retained in database > > Other things to consider are: > * can save some stuff, but not all > * security / privacy matters > * database maintenance / clean up procedures > * length of session > * ?????? > > I am welcoming any comments, for and against, just curious to know if > there are any "best practices" in this area. > > -- > NZ PHP Users Group: http://groups.google.com/group/nzphpug > To post, send email to [email protected] > To unsubscribe, send email to > [email protected] -- NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected]
