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
  • mysql-test
  • r
  • datetime_456.result
Find file BlameHistoryPermalink
  • Sergei Golubchik's avatar
    MDEV-456 An out-of-range datetime value (with a 5-digit year) can be created and cause troubles · a44331ab
    Sergei Golubchik authored Aug 29, 2012
    fix Item_func_add_time::get_date() to generate valid dates.
    Move the validity check inside get_date_from_daynr()
    instead of relying on callers
    (5 that had it, and 2 that did not, but should've)
    a44331ab

Replace datetime_456.result

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