[
https://issues.apache.org/jira/browse/TRAFODION-1242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Smits updated TRAFODION-1242:
------------------------------------
Fix Version/s: (was: 2.1-incubating)
2.2.0
> LP Bug: 1457207 - Create table and constraint using the same name returns
> error 1043
> ------------------------------------------------------------------------------------
>
> Key: TRAFODION-1242
> URL: https://issues.apache.org/jira/browse/TRAFODION-1242
> Project: Apache Trafodion
> Issue Type: Bug
> Components: sql-exe
> Reporter: Weishiun Tsai
> Assignee: Anoop Sharma
> Priority: Critical
> Fix For: 2.2.0
>
>
> Create a table with a constraint that has the same name as the table itself
> now returns a perplexing 1043 error complaining that the constraint already
> exists. This is a regression introduced sometime between the v0513 build and
> the v0519 build. It had been working fine until the v0513 build where SQL
> tests were last run.
> This is seen on the v0513 build.
> --------------------------------------------------------------
> Here is the entire script to reproduce it:
> create schema mytest;
> set schema mytest;
> create table t1 (c1 int , c2 int constraint t1 check (c2 > 10));
> drop schema mytest cascade;
> --------------------------------------------------------------
> Here is the execution output:
> >>create schema mytest;
> --- SQL operation complete.
> >>set schema mytest;
> --- SQL operation complete.
> >>create table t1 (c1 int , c2 int constraint t1 check (c2 > 10));
> *** ERROR[1043] Constraint TRAFODION.MYTEST.T1 already exists.
> *** ERROR[1029] Object TRAFODION.MYTEST.T1 could not be created.
> --- SQL operation failed with errors.
> >>drop schema mytest cascade;
> --- SQL operation complete.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
