This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
1. Connect to "travel" Java DB. 2. Rightclick some table and choose "Add Column...". 3. Enter name for the column and press "OK". 4. Rightclick added column. Result: Item "Delete" exists, but it is disabled, so there is no possibility to remove added column without SQL Editor.
Which version of Derby? The ability to drop columns was introduced in a relatively recent version (10.3.1.4). Of course, we do not enable the Delete action for version that do support DROP COLUMN. Still, I would argue this is a P3, because Derby has not supported this functionality for a long time.
I use Derby supplied with GlassFish V2 UR2, version 10.2.2.1. But I don't agree that this issue is P3, since customer see this item, but can't use it. And it can mislead, since customer can't know that the ability to drop columns was introduced in a relatively recent version.
How do you propose that the DB Explorer behave when a version of Derby which doesn't support DROP COLUMN is used?
Context menu shouldn't have this item, if it is useless, and customer won't be misled.
I think this should be an enhancement, not a defect. It is certainly possible to determine the major and minor version of the database using the meta data. Support for certain features of the database engine (like DROP COLUMN) based on minimum version could be stored in a plist kind of file. That sounds like an enhancement.
I agree adding support for Delete Column on a database that didn't used to support it is an enhancement. I don't think it's a P2 to have an action visible but disabled.
Reassigned to new owner.
No plan to change it