You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "Alice Chen (JIRA)" <ji...@apache.org> on 2015/07/22 20:14:23 UTC
[jira] [Created] (TRAFODION-149) LP Bug: 1250183 - Clustering key
conflicts with primary keys
Alice Chen created TRAFODION-149:
------------------------------------
Summary: LP Bug: 1250183 - Clustering key conflicts with primary keys
Key: TRAFODION-149
URL: https://issues.apache.org/jira/browse/TRAFODION-149
Project: Apache Trafodion
Issue Type: Bug
Components: sql-general
Reporter: Weishiun Tsai
Assignee: Anoop Sharma
Priority: Critical
When specifying STORE BY in a query together with PRIMARY KEY, the STORE BY seems to overwrite the PRIMARY KEY list. The following example executes fine on SQ, but it gets an 8102 unique constraint error on Traf:
>>set schema seabase.mytest;
--- SQL operation complete.
>>create table t (a int not null, b int not null, c int not null, d int, primary
key (a, b, c)) store by (a);
--- SQL operation complete.
>>insert into t values (1, 1, 1, 1), (1, 2, 2, 2);
*** ERROR[8102] The operation is prevented by a unique constraint.
--- 0 row(s) inserted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)