Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • M mariadb
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Kirill Smelkov
  • mariadb
  • Repository

Switch branch/tag
  • mariadb
  • sql
  • sql_yacc.yy
Find file BlameHistoryPermalink
  • mats@mysql.com's avatar
    Bug#7879: Using TL_READ_NO_INSERT locks instead of TL_READ locks when · 625f7f0d
    mats@mysql.com authored Feb 15, 2005
    reading tables in "complex" SQL statements. If inserts happen in a
    table being read, the statements have no serialization order and the
    change can therefore not be reproduced on the slave.
    625f7f0d

Replace sql_yacc.yy

Attach a file by drag & drop or click to upload


Cancel
GitLab will create a branch in your fork and start a merge request.
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7