tdbc::mysql

Ticket Change Details
Login
Bounty program for improvements to Tcl and certain Tcl packages.
Overview

Artifact ID: 589c0502d3903ec406ce26b46364b67318787db9a1bfd8003daef0ebe1185a70
Ticket: 9bf0e3e2e71a07d57923a5b789cd78f8ac925fbc
-isolation configuration option
User & Date: anonymous 2020-02-16 10:59:28
Changes

  1. Change foundin to "1.1.1 (latest trunk)"
  2. Change icomment to:

    Currently the config handling for -isolation uses SQL commands like: SET TRANSACTION ISOLATION LEVEL READ SERIALIZABLE to effect the change. This only sets the transaction isolation level for the next transaction, after which it reverts to whatever the current session isolation level is. To set the session isolation level instead (which persists on this connection until changed to something else), it should use SET SESSION TRANSACTION ISOLATION LEVEL SERIALIZABLE instead.

    This fixes the failure on test tdbc::mysql-19.11, which uses SELECT '', LCASE(REPLACE(@@TX_ISOLATION, '-', '')) to interrogate the current session isolation level - @@tx_isolation reports the session transaction isolation level, and there is no way to report on the level set for the next transaction (which is what "SET TRANSACTION ISOLATION LEVEL foo" does)

  3. Change login to "anonymous"
  4. Change mimetype to "text/x-fossil-plain"
  5. Change private_contact to "54152f94cb1628c0c148b4b5708ace53216227b0"
  6. Change severity to "Severe"
  7. Change status to "Open"
  8. Change title to "-isolation configuration option"
  9. Change type to "Code_Defect"