[
https://issues.apache.org/jira/browse/DERBY-4681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995786#comment-12995786
]
Grzegorz Łyp commented on DERBY-4681:
-------------------------------------
I understand the standard way of thinking. From the practical point of view,
having many views that create nesting tree makes the drop of the column very
difficult task. The typical situation is the upgrade of the existsing database
with many objects. If the upgrade drops column it is necessary to create all
the depending views again. Such operation could be done automatically by the
derby engine. It might be an option to alter table, but great thing to use.
> Dropping a column in the table drops the views that use this table
> ------------------------------------------------------------------
>
> Key: DERBY-4681
> URL: https://issues.apache.org/jira/browse/DERBY-4681
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.3.1.4, 10.3.2.1, 10.3.3.0, 10.4.1.3, 10.4.2.0,
> 10.5.1.1, 10.5.2.0, 10.5.3.0, 10.6.1.0
> Environment: Windows 7 Enterprise, JDK SE 1.6 u20
> Reporter: Grzegorz Łyp
> Priority: Critical
> Labels: derby_triage10_8
>
> If i have a table and a view that uses this table, after dropping a column
> from this table the whole view is also dropped.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
