Hello, list,
I'm having a weird issue with table locking. I'm running MySQL 3.23 on a
Win2k server, used for eCommerce applications.
All settings appear to be in order, that is, KeepAlive is 30, connection
pooling is on, with a timeout of 30.
The tables in any given database seem to remain locked for as long as 30
minutes after all clients have gone away, and all ODBC connections have
completed.
These are MyISAM tables.
The long and short of it is that I am using PS MySQL Studio to remotely
administer the db, and testing the software product concurrently. I need
the software to lock the table, of course, but only for the amount of time
I have specified, i.e. for 30 seconds after the client disappears, which
should be 30 seconds after the KeepAlive times out, which is also 30
seconds. So, it shouldn't be any more than 1 minute after all clients go
away, before I can commit a change to a table, right? I am also not quite
sure if connection pooling even matters. Shouldn't ODBC just reuse the same
connection if the KeepAlive times out before the ODBC pool, eh, so the 30
seconds for the inactive connection through the browser to time out is all
that should matter? Am I missing something here?
I am using iHTML for this particular eCommerce app, BTW. If anyone is
familiar with this and knows if the issue is in iHTML, let me know that as
well.
TIA,
--Scott Brown
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
