Warning: Can't synchronize with repository "(default)" (Unsupported version control system "svn": No module named svn). Look in the Trac log for more information.

Changes between Version 3 and Version 4 of SqlobjectCaching


Ignore:
Timestamp:
11/28/05 09:41:42 (14 years ago)
Author:
kevin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SqlobjectCaching

    v3 v4  
    99The TurboGears !AutoConnectHub and !PackageHub classes automatically call SQLObject's connectionForURI as needed to get a database connection. connectionForURI caches SQLObject DBConnection objects, so that only one DBConnection is maintained for a given URI. (Note: As of this writing, TurboGears works around this cache for sqlite. There is a problem with SQLObject's connection pooling for sqlite because sqlite requires that a given connection only be used on the thread on which it was created and SQLObject does not maintain this.) 
    1010 
    11 The DBConnection object maintains the pool of underlying database connections and also maintains the object instance cache. DBConnection takes a "cache" parameter that is passed in to the CacheSet object that is created (more about CacheSet coming up). The cache parameter defaults to True. Setting this to false (?cache=0 in your connection URI) will cause items to be only "partially cached" (more below). 
     11The DBConnection object maintains the pool of underlying database connections and also maintains the object instance cache. DBConnection takes a "cache" parameter that is passed in to the !CacheSet object that is created (more about !CacheSet coming up). The cache parameter defaults to True. Setting this to false (?cache=0 in your connection URI) will cause items to be only "partially cached" (more below). 
    1212 
    13 == !CacheSets == 
     13== CacheSets == 
    1414 
    1515The !CacheSet for a DBConnection maintains a separate instance cache (!CacheFactory) for each class.