Uploaded image for project: 'MariaDB ColumnStore'
  1. MariaDB ColumnStore
  2. MCOL-1080

MariaDB ColumnStore does not support primary/unique keys

Details

    • New Feature
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Won't Do
    • None
    • N/A
    • N/A
    • None
    • 1.0.11

    Description

      1.not support replce into table_name
      2.not support load data replce into

      Attachments

        Activity

          It appears to work to me. Can you please give us more details on the problem?

          MariaDB [test]> replace into t1 values (1,2);
          Query OK, 1 row affected (0.26 sec)
           
          MariaDB [test]> select * from t1;
          +------+------+
          | a    | b    |
          +------+------+
          |    1 |    2 |
          +------+------+
          1 row in set (0.10 sec)
           
          MariaDB [test]> replace into t1 values (2,3);
          Query OK, 1 row affected (0.10 sec)
           
          MariaDB [test]> select * from t1;
          +------+------+
          | a    | b    |
          +------+------+
          |    1 |    2 |
          |    2 |    3 |
          +------+------+
          2 rows in set (0.02 sec)
          

          LinuxJedi Andrew Hutchings (Inactive) added a comment - It appears to work to me. Can you please give us more details on the problem? MariaDB [test]> replace into t1 values (1,2); Query OK, 1 row affected (0.26 sec)   MariaDB [test]> select * from t1; +------+------+ | a | b | +------+------+ | 1 | 2 | +------+------+ 1 row in set (0.10 sec)   MariaDB [test]> replace into t1 values (2,3); Query OK, 1 row affected (0.10 sec)   MariaDB [test]> select * from t1; +------+------+ | a | b | +------+------+ | 1 | 2 | | 2 | 3 | +------+------+ 2 rows in set (0.02 sec)
          hiller1 hiller1 added a comment -

          MariaDB [test]> select * from t1;
          ------

          id

          ------

          1

          ------
          1 row in set (0.01 sec)

          MariaDB [test]> replace into t1 values(1);
          Query OK, 1 row affected (0.17 sec)

          MariaDB [test]> select * from t1;
          ------

          id

          ------

          1
          1

          ------
          2 rows in set (0.01 sec)

          MariaDB [test]> select @@version_comment;
          ----------------------

          @@version_comment

          ----------------------

          Columnstore 1.0.11-1

          ----------------------
          1 row in set (0.00 sec)

          record 1 can not be overwritten,there are duplicate records.

          hiller1 hiller1 added a comment - MariaDB [test] > select * from t1; ------ id ------ 1 ------ 1 row in set (0.01 sec) MariaDB [test] > replace into t1 values(1); Query OK, 1 row affected (0.17 sec) MariaDB [test] > select * from t1; ------ id ------ 1 1 ------ 2 rows in set (0.01 sec) MariaDB [test] > select @@version_comment; ---------------------- @@version_comment ---------------------- Columnstore 1.0.11-1 ---------------------- 1 row in set (0.00 sec) record 1 can not be overwritten,there are duplicate records.

          MariaDB ColumnStore has no primary/unique keys so REPLACE is basically an INSERT. The behaviour is technically correct.

          Instead I can change this ticket into a feature request for primary keys if that is what is desired?

          LinuxJedi Andrew Hutchings (Inactive) added a comment - MariaDB ColumnStore has no primary/unique keys so REPLACE is basically an INSERT. The behaviour is technically correct. Instead I can change this ticket into a feature request for primary keys if that is what is desired?
          hiller1 hiller1 added a comment -

          thanks!

          hiller1 hiller1 added a comment - thanks!
          hiller1 hiller1 added a comment -

          If can support overwrite is very good.

          hiller1 hiller1 added a comment - If can support overwrite is very good.

          Ticket has been updated accordingly and changed to a feature request.

          Priority is currently low as this is a very large project to implement and the expected performance cost of using the implementation will be high.

          LinuxJedi Andrew Hutchings (Inactive) added a comment - Ticket has been updated accordingly and changed to a feature request. Priority is currently low as this is a very large project to implement and the expected performance cost of using the implementation will be high.

          People

            toddstoffel Todd Stoffel (Inactive)
            hiller1 hiller1
            Votes:
            1 Vote for this issue
            Watchers:
            2 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.