If you want to analyse cart behavior (e.g. abandonment etc) it's useful to have this information -Nick
On Thu, Jul 15, 2010 at 7:15 PM, Neven MacEwan <[email protected]> wrote: > If your connecting to a database put all your data in the DB full stop, > there is not benefit in storing data in 2 places (unless you consider > unnecessary complexity a benefit) > > N >> >> 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]
