I'm wanting to apply this patch (_v8_) to the 10.2.1.6 sources (the
latest released version). But applying the patch to these sources fails.
What are my options?
Its important that I have a version that allows databases to be upgraded
with future versions, so I was hoping to stick as closely to the
released version as possible, and avoid the "this database can't be
upgraded because it was created by a beta version of derby" problem.
Thanks
Tim
Bryan Pendleton (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-1489?page=all ]
Bryan Pendleton resolved DERBY-1489.
------------------------------------
Fix Version/s: 10.3.0.0
Resolution: Fixed
Derby Info: (was: [Patch Available])
Thanks very much to all the reviewers, and particularly to Mamta who checked
several versions of this patch.
I've committed the _v8_ version of the patch to subversion as revision 453420.
I'm marking this issue resolved; for now, we have an undocumented new feature
which does not work with sqlAuthorization mode. I hope to find time soon to
work on the two followon issues: DERBY-1909 to fix the sqlAuthorization
problem, and DERBY-1926 to provide documentation.
Provide ALTER TABLE DROP COLUMN functionality
---------------------------------------------
Key: DERBY-1489
URL: http://issues.apache.org/jira/browse/DERBY-1489
Project: Derby
Issue Type: New Feature
Components: Documentation, SQL
Affects Versions: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.2.1.6, 10.1.2.1,
10.1.3.0, 10.1.3.1
Reporter: Bryan Pendleton
Assigned To: Bryan Pendleton
Fix For: 10.3.0.0
Attachments: drop_column_v5_grant_tests.diff,
drop_column_v6_grant_not_implemented.diff,
drop_column_v7_suggestions_from_mamta.diff, drop_column_v8_restored_tests.diff,
dropColumn_2.diff, dropColumn_v3_view_drop.diff, dropColumn_v4_grant_tests.diff
Provide a way to drop a column from an existing table. Possible syntax would be:
ALTER TABLE tablename DROP COLUMN columnname CASCADE / RESTRICT;
Feature should properly handle columns which are used in constraints, views,
triggers, indexes, etc.
