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

NO_KEY_OPTIONS SQL mode has no effect on engine key options

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Fixed
    • N/A
    • 11.7.1
    • Vector search
    • None

    Description

      I'm not sure whether it should (have any effect). The documentation says that it removes "MariaDB-specific options", and I guess distance and m are MariaDB-specific, so it seems to fit. On the other hand, since the index itself is MariaDB-specific, it doesn't make much sense to try to keep its options compatible with something.

      create table t (v vector(1) not null, vector(v) distance=cosine m=42);
      show create table t;
      set sql_mode=NO_KEY_OPTIONS;
      show create table t;
       
      # Cleanup
      drop table t;
      

      7aab5e35d714fc3b6de68f5158072d5ecdf62faa

      set sql_mode=NO_KEY_OPTIONS;
      show create table t;
      Table	Create Table
      t	CREATE TABLE `t` (
        `v` vector(1) NOT NULL,
        VECTOR KEY `v` (`v`) `distance`=cosine `m`=42
      ) ENGINE=MyISAM DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_uca1400_ai_ci
      

      Attachments

        Issue Links

          Activity

            People

              serg Sergei Golubchik
              elenst Elena Stepanova
              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.