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
You need to sign in or sign up before continuing.
  • mariadb
  • sql
  • sql_update.cc
Find file BlameHistoryPermalink
  • Justin.He/justin.he@dev3-240.dev.cn.tlan's avatar
    Bug#27127, Incorrect behaviour of timestamp column with DEFAULT CURRENT_TIMESTAMP · 0bbae247
    Justin.He/justin.he@dev3-240.dev.cn.tlan authored Mar 22, 2007
    correct the bitmap_set_bit when a field is timestamp and described 
    with default CURRENT_TIMESTAMP or on update CURRENT_TIMESTAMP,
    then it will reduce a little time cost when the field doesnot need 
    to write.
    0bbae247
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7