some time ago i posted a list of my ideas along this..
http://groups.google.com/group/sqlalchemy/browse_thread/thread/d886963fe58d7abb
be ware: its all pure theory.
-1 (horizontal) (eager) loading ONLY of the needed row attributes,
also hierarhicaly (a.b.c.d)
-2 (vertical) simultanously
thinking of it... the attributes has to be deferred/None, and set-up
externaly by the wrapping smartie, e.g. UI pager or whatever.
but i have no idea how it can be done most nicely... some synonim()
that returns some.cache[ mycol] else fallsback to self._mycol?
On Wednesday 28 May 2008
Yep, exactly that. It would speed up my (UI) app immensely. Any ideas
how to approach something like that?
On May 28, 5:07 pm, [EMAIL PROTECTED] wrote:
some time ago i posted a list of my ideas along
this..http://groups.google.com/group/sqlalchemy/browse_thread/thread/d88696...
be ware:
On Wednesday 28 May 2008 15:49:16 Koen Bok wrote:
Yep, exactly that. It would speed up my (UI) app immensely. Any
ideas how to approach something like that?
thinking of it... the attributes has to be deferred/None, and
set-up externaly by the wrapping smartie, e.g. UI pager or
whatever. but
you'd like to do query caching. If it were me, I'd implement this at
the SQL level by intercepting statements for particular tables, and
matching the criteria to a cached value. Inspection of the criteria
would determine if it was a candidate for caching or not (or you could
