Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • M mariadb
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • 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
  • mariadb
  • sql
  • sql_base.cc
Find file BlameHistoryPermalink
  • unknown's avatar
    Fix for BUG#3063 "Don't mark an auto DROP TEMP TABLE as 'killed' in the binlog"; · c1f9f3b6
    unknown authored Mar 04, 2004
    even if the thread was killed, we write the DROP with error_code=0.
    This will remove unneeded stops on slave, and will lose nothing:
    if a real update was killed, this real update will be logged with the
    nonzero error code and will cause the stop on slave.
    
    
    c1f9f3b6
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7