On Nov 2, 11:55 pm, Michael Bayer <[EMAIL PROTECTED]> wrote: > I'd have to disagree here; SQLAlchemy is a database access library, > its not a caching or application framework. Providing a thread- > synrchronized caching container would be the job for Pylons or some > other third party software (or roll your own). Also this solution > wouldn't work for application models that are non-threaded (like > process-split models); out-of-sync requests would still hit a locked > database.
Ok, after thinking some more I agree with the above. I'm not really sure whether this can be fixed in general, however, at the AJAX or web server level effectively. If I started the transaction earlier and upgraded it to a write transaction when I initially load the cart then I could ensure that this failure scenario wouldn't occur. Is that currently possible? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
