Re: [Sqlalchemy-users] caching

On 3/26/06, Florian Boesch <[EMAIL PROTECTED]> wrote: So how do you scale/split your application across multiple data accessingservers (short of writing an application server)?What problems does an identity map pose to multiple client processes? I'm confused because you seem to imply that if you co

Re: [Sqlalchemy-users] caching

So how do you scale/split your application across multiple data accessing servers (short of writing an application server)? Calling objectstore.clear() everywhere? Quoting Michael Bayer <[EMAIL PROTECTED]>: > theres no caching in SQLAlchemy. theres an identity map which has > some of the same e

Re: [Sqlalchemy-users] caching

theres no caching in SQLAlchemy. theres an identity map which has some of the same effects as a cache. basically, if you have already loaded your object into the current session, thats it. if you load it again, its going to use the same one you have, unless you clear the session, or refr

[Sqlalchemy-users] caching

Seemingly SA is fairly liberal with interpreting my wish to get stuff from the database. So what's the pattern to deal with "session" "caching"? I hear there's expunge etc. now, and expire, but that's all when I know what objects I want to have removed/expired/refreshed. Fact is, I don't, I would

[Sqlalchemy-users] Caching compiled selects

I wrote a private method "_select" to cache compiled selects as attributes of the class instance that is working with the selects. Example usage is as follows: > def _select(self, *args, **kw): > """ > Compiles and caches a select object, returning a reference to it. >