Leon Brocard <[EMAIL PROTECTED]> writes:
> Piers Cawley sent the following bits through the ether:
>
> > And it doesn't do it very well. You have to keep track of whether
> > stuff changed deep in the hash yourself.
>
> Indeed. Got a better idea? (while being as configurable as A::S?)
> It's a bit too complicated, and no-one unerstands code written with it
> (Mark, Simon ;-)
Well, I stash my shopping basket back into a simple table. The basket
itself keeps track of a dirty/clean flag (Data gets loaded from
database by my Vendor::Setup handler, the dirty flag gets unset. And
registers a cleanup handler that checks the dirty flag and writes dirty
baskets back out to the database.)
It's probably a good idea to have your session and basket tables in
the same database as your product database, but not essential.
I've still not quite finalized the database structure for my
session/basket data though. And I know damn fine that I shouldn't
really be writing as much SQL as I am doing...
--
Piers
