Thanks for your reply. Should we move this discussion to
[EMAIL PROTECTED]
> Also, notice that unless your application is under _extreme_ load,
none
> of these SET queries will are likely to have an impact on the
> performance of your application.
I was hoping someone would reply saying that SET SESSION TRANSACTION
ISOLATION LEVEL READ COMMITTED would be ignored for MyISAM tables. I may
open an official support call to verify.
> If you're using a newer version of our JDBC driver (3.1.x), you can
> always add "useLocalSessionState=true" to avoid having to do _some_ of
> these queries to the database.
I installed the 3.1.10 driver and tried that but I can not tell a
difference and don't know how to verify. I submitted it to the
coldfusion database access forum for help.
I noticed the MySQL Connector/J Documentation for useLocalSessionState
says...
Should the driver refer to the internal values of autocommit and
transaction isolation that are set by Connection.setAutoCommit() and
Connection.setTransactionIsolation(), rather than querying the database?
Can you elaborate any more on this? From the description it makes it
sound like it wouldn't set autocommit or session transaction isolation
at all. Then again, I wonder if it is saying that yes it will set them
both, it just will not query the database to check its setting before it
does (getting rid of show variables?). Humm.
Note-I also set the global TRANSACTION ISOLATION LEVEL READ COMMITTED
thinking that if it was already set at the global level then it would
not be set at the session level (after the show variables). But that
didn't help.
Thanks,
Daniel
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
