Forum OpenACS Q&A: closing all db handles...

Collapse
1: closing all db handles...
Posted by David Kuczek on 07/31/02 12:59 PM
In a proc I want to close all database handles no matter how many are
opened and what their variable names are... How can I do this?
Collapse
2: Response to closing all db handles... (response to 1)
Posted by Dan Wickstrom on 07/31/02 01:42 PM
Try calling db_release_unused_handles.
Collapse
3: Response to closing all db handles... (response to 1)
Posted by David Kuczek on 07/31/02 02:07 PM
Thanks Dan,

but any idea for 3.2.5? It can't be ported too straightforwardly...

Collapse
4: Response to closing all db handles... (response to 1)
Posted by Dan Wickstrom on 07/31/02 02:29 PM
Oh 3.2.5...

If it's not too much of a problem to rewrite queries, you can backfit the openacs 4 db api to 3.2.5.  I know there are several versions of the openacs 4 db api ported to 3.2.5 floating around (search the bboards).  If not, there's no easy way to do it from tcl, unless you somehow keep track of all the handles that have been allocated, which is what the oacs 4 db api does.

If you want to write a tcl extension in 'c', then you could also create a proc for closing all of the handles in the current connection thread.  Db handles are stored in thread-specific data, so it's easy to get access to them from a 'c'-function.

Collapse
5: Response to closing all db handles... (response to 1)
Posted by Michael A. Cleverly on 09/04/02 09:34 AM
If you really want to close all database handles (that your thread has access to), and you don't care how they were opened, then I'd do this. 
set total_num_handles [expr {5 + 5 + 5}]
for {set i $total_num_handles} {$i >= 0} {incr i -1} {
    catch { ns_db releasehandle nsdb$i }
}
Totally hackish, but it should meet the "no matter how many were opened and what their variable names were" criteria. :^) I'd suggest backporting the database API though.