You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "Suresh Subbiah (JIRA)" <ji...@apache.org> on 2015/10/08 01:15:27 UTC
[jira] [Updated] (TRAFODION-1256) LP Bug: 1461134 - ALTER TABLE
DROP COLUMN does not check for dependent objects
[ https://issues.apache.org/jira/browse/TRAFODION-1256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Suresh Subbiah updated TRAFODION-1256:
--------------------------------------
Assignee: Anoop Sharma
> LP Bug: 1461134 - ALTER TABLE DROP COLUMN does not check for dependent objects
> ------------------------------------------------------------------------------
>
> Key: TRAFODION-1256
> URL: https://issues.apache.org/jira/browse/TRAFODION-1256
> Project: Apache Trafodion
> Issue Type: Bug
> Components: sql-cmu
> Reporter: Cliff Gray
> Assignee: Anoop Sharma
> Priority: Critical
> Fix For: 2.0-incubating
>
>
> Before dropping a column, a check should be made for objects that depend on the column.
> Example:
> CREATE TABLE T1 (A INT NOT NULL PRIMARY KEY, B INT);
> CREATE VIEW V1 AS SELECT B FROM T1;
> ALTER TABLE T1 DROP COLUMN B; -- should fail
> At a minimum RESTRICT behavior should be supported. Ideally, CASCADE would be supported as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)