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.
component: computing nodes | priority: minor | resolution: Not-a-bug
2021-06-17 18:03:43: @jd-zhang created the issue
sql code:
drop table if exists uv_iocu_tab cascade;
create table uv_iocu_tab (a int unique, b varchar(50));
insert into uv_iocu_tab values(1,'x');
create view uv_iocu_view as
select b as bb, a as aa, uv_iocu_tab::varchar(50) as cc from uv_iocu_tab;
select * from uv_iocu_view;
ERROR: Kunlun-db: Must specify whole-row target left-most.
Issue migrated from trac ticket # 113
component: computing nodes | priority: minor | resolution: Not-a-bug
2021-06-17 18:03:43: @jd-zhang created the issue