Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-5260

discovery with sql is too restrictive

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.0.5
    • 10.0.6
    • None
    • None

    Description

      Currently the SQL syntax that is accepted for sql-based discovery (in TABLE_SHARE::init_from_sql_statement_string() restricts the CREATE TABLE statement to a certain subset of all allowed syntaxes. In particular, one cannot use the ENGINE= clause. This is unnecessary restrictive, one should be able to specify ENGINE=xxx as long as xxx is the engine performing the discovery. Just as before, one should not be able to alter table's engine during the discovery.

      Attachments

        Activity

          serg Sergei Golubchik created issue -
          serg Sergei Golubchik made changes -
          Field Original Value New Value
          Status Open [ 1 ] In Progress [ 3 ]
          serg Sergei Golubchik made changes -
          Resolution Fixed [ 1 ]
          Status In Progress [ 3 ] Closed [ 6 ]
          serg Sergei Golubchik made changes -
          Workflow defaullt [ 29633 ] MariaDB v2 [ 44371 ]
          ratzpo Rasmus Johansson (Inactive) made changes -
          Workflow MariaDB v2 [ 44371 ] MariaDB v3 [ 63704 ]
          serg Sergei Golubchik made changes -
          Workflow MariaDB v3 [ 63704 ] MariaDB v4 [ 147209 ]

          People

            serg Sergei Golubchik
            serg Sergei Golubchik
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.