tdbc::mysql

Ticket Change Details
Login
Overview

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

  1. foundin changed to: "1.1.1 (latest trunk)"
  2. icomment:
    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. login: "anonymous"
  4. mimetype: "text/x-fossil-plain"
  5. private_contact changed to: "54152f94cb1628c0c148b4b5708ace53216227b0"
  6. severity changed to: "Severe"
  7. status changed to: "Open"
  8. title changed to: "-isolation configuration option"
  9. type changed to: "Code_Defect"