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_cache.cc
Find file BlameHistoryPermalink
  • evgen@moonbone.local's avatar
    Fix bug #13424 locking view with query cache enabled crashes server · 0032165a
    evgen@moonbone.local authored Sep 26, 2005
    For LOCK view is opened but not prepared thus leaving 'table' field set to
    NULL. invalidate_locked_for_write() wasn't checking that and call to 
    invalidate_table(NULL) crashes server.
    
    To invalidate_locked_for_write() added check that ensures that table is
    completely opened.
    0032165a
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7