I don't know which backend you are using, but I had a few problems
working with mysqltcl. As one might expect, if a child process stays
idle too long the backend drops the connection, and it happened every
night on the computer where I was developing the application.
mysqltcl has a 'status' method and I thought I could have information
about the dbms connection from it, but actually it didn't say anything
useful (what it returned was even wrong and misleading). This was a few
years ago and this support in mysqltcl might have improved now.
The only way I found to get around it was closing the connection once
the request had been served and reopening it every time. Shamefully
expensive.
-- Massimo
On 10/29/2010 06:57 AM, Clif Flynt wrote:
Thanks. I was suspecting something like this.
Eventually, all of the children will have a ::db1 procedure, and
all will be happy.
I was afraid that I was causing some unnecessary thrashing, but I
guess it's necessary after all.
Happy Tcl'ing,
Clif
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
