1.0.11

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)

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

------

------
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;
------

------

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

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

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

----------------------
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?

thanks!

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.