The answer doesn't need to be pylons specific. I just happen to be
using this framework, so this group seemed like a good place to start.
I'm looking to store info thats a bit more complex than just a item
number, so I'm considering storing temporary items created in guest
sessions in a table
On 1/25/10 09:57 , Matt Woolnough wrote:
The answer doesn't need to be pylons specific. I just happen to be
using this framework, so this group seemed like a good place to start.
I'm looking to store info thats a bit more complex than just a item
number, so I'm considering storing temporary
On Jan 25, 4:36 am, Wichert Akkerman wich...@wiggy.net wrote:
Beaker sessions.
either beaker sessions, or just use a beaker session id as the
shopping cart / user id
you could do a dbtable that has this:
table: cart
id bigserial primary key not null,
session_id char(32) unique ,
I use beaker sessions for something similar. Basically, i have sqlite
based session (so its there if my server restarts), and I serialize the
entire shopping cart object into the session.
Once a user logs in, the session object is converted to a 'real'
shopping cart which, in my case, is
Thanks guys for your input.
I found a couple of threads on stackoverflow on similar questions:
http://stackoverflow.com/questions/1969711/best-way-to-place-temporary-data-for-an-webapp
http://stackoverflow.com/questions/964476/store-in-session-data-vs-store-in-sql-database-for-temporary-data
