Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
M MariaDB
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • nexedi
  • MariaDB
  • Repository

Switch branch/tag
  • mariadb
  • mysql-test
  • std_data
  • mdev17909#P#p20181128.MYI
Find file HistoryPermalink
  • Sergei Golubchik's avatar
    MDEV-17909 Problem by MariaDB Update 10.1.32 -> 10.2.19 (Incorrect information in file: .frm) · fca44b7c
    Sergei Golubchik authored Dec 13, 2018
    use frm_version, not mysql_version when parsing frm
    
    In particular, virtual columns are stored according to
    frm_version. And CHECK TABLE will overwrite mysql_version
    to the current server version, so it cannot correctly
    describe frm format.
    fca44b7c
mdev17909#P#p20181128.MYI 1 KB

Download (1 KB)

Replace mdev17909#P#p20181128.MYI

Attach a file by drag & drop or click to upload


Cancel
A new branch will be created in your fork and a new merge request will be started.
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7