Re: [SQLObject] connection document on wiki

[Ian B. <ia...@co...>]

Charles Brandt wrote:
> Hi,
> 
> I've been revisiting the concept of connections and caching in SQLObject to
> get a few of the nuances straight in my head.  In the process I tried to jot
> these concepts down in writing and posted them on the SQLObject Wiki site
> here:
> http://wiki.sqlobject.org/connections.html
> 
> This process lead me to two big questions on the topic:
> 
> 1.  Is there a way to manually close a connection?

Hmm... no.  And since SQLObject does pooling it's not trivial.

> 2.  Is there a way to manually expire the cache of a connection?

connection.cache.expireAll() -- that won't removed the cached objects, 
but it will only hold weak references.

> In a prior mailing list thread I think I read that objects are not coupled
> with connections, so maybe question 2 is worded incorrectly.  (this is
> specifically asked with the method of passing a connection to a object in
> mind).

They are coupled rather strongly to connections.

> On a more general note I'd be very interested to hear details on how others
> deal with connections in their SQLObject applications, especially
> multi-process applications.

Yes, that's still a bit of an open issue.  It's hard, because it really 
depends on how accurate you want to be -- you can be very accurate by 
checking each time an attribute is accessed, but that's really 
inefficient, and may give you an inconsistent view.  I'd be interested 
in hearing other people's thoughts as well.

-- 
Ian Bicking  /  ia...@co...  / http://blog.ianbicking.org