i couldn't find anything on trac earlier for `coerce_from_config` i'd be happy to whip up a patch for the .8 branch that updates coerce_from_config to support all the create_engine kwargs. i have no idea how to do that for the .9 branch though.
my sql is pretty optimized as is, with everything being cached. i need to look at some server side and query optimizations next. anyways, 99% of the app works like this: - select ids from dogpile.cache; Failover to sqlalchemy - select records from dogpile.cache, based on id; failover to sqlalchemy - select record relationships from dogpile.cache (lazyloaded properties) based on id, failover to sqlalchemy a 'cache optimizer' will inspect the loaded objects for cacheable relationships, then prime the cache with those ( which will appear when lazyloaded relations are hit ). sample web page: - regular sqlalchemy query = ~600 selects - sqlalchemy with eagerloading = ~250 selects - using cached objects, but no request priming ( sqlalchemy does eagerloading ) = ~150 selects - cached objects with request priming = ~34 selects that's with an empty cache. on a full cache, sqlalchemy is never hit. and yeah - this builds up pretty complex objects in the cache. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/groups/opt_out.
