KunlunBase is a distributed relational database management system(RDBMS) with complete NewSQL capabilities and robust transaction ACID guarantees and is compatible with standard SQL. Applications which used PostgreSQL or MySQL can work with KunlunBase as-is without any code change or rebuild because KunlunBase supports both PostgreSQL and MySQL connection protocols and DML SQL grammars. MySQL DBAs can quickly work on a KunlunBase cluster because we use MySQL as storage nodes of KunlunBase. KunlunBase can elastically scale out as needed, and guarantees transaction ACID under error conditions, and KunlunBase fully passes TPC-C, TPC-H and TPC-DS test suites, so it not only support OLTP workloads but also OLAP workloads. Application developers can use KunlunBase to build IT systems that handles terabytes of data, without any effort on their part to implement data sharding, distributed transaction processing, distributed query processing, crash safety, high availability, strong consistency, horizontal scalability. All these powerful features are provided by KunlunBase. KunlunBase supports powerful and user friendly cluster management, monitor and provision features, can be readily used as DBaaS.
2022-05-06 11:34:35: zhaowei@zettadb.com created the issue
INSERT [INTO] t1 [column-list] VALUES/VALUE()
INTO is optional in INSERT STMT, also, VALUES and VALUE both OK.
INSERT [INTO] SET assignment list
single row insert stmt, INTO is optional
REPLACE [INTO] ... [column-list] VALUE/VALUES
INTO is optional, and VALUES and VALUE both OK.
REPLACE [INTO] ... SET assignment_list
single row REPLACE stmt, INTO is optional
REPLACE [INTO] ... [column-list] SELECT
INTO is optional, the SELECT clause provides source rows, and SELECT's target list must match the column-list which by default is the table's all columns
allow IGNORE for UPDATE stmt
With the IGNORE modifier, the update statement does not abort even if errors occur during the update.
Implement this escape rule: Rows for which duplicate-key conflicts occur on a unique key value are not updated.
But don't implement this ignorance: Rows updated to
values that would cause data conversion errors are updated to the closest valid values instead.
jd-zhang
commented
2 years ago
Issue migrated from trac ticket # 644 www.kunlunbase.com
component: computing nodes | priority: major
2022-05-06 11:34:35: zhaowei@zettadb.com created the issue