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.
Created attachment 107291 [details] Proposed patch (see comment) Hey, the schema property of the connection node in the database-explorer should be editable. A college of mine noticed this today and got a bit annoyed by it. So I had a look at it this evenning and the fix seems so easy (see patch). It applies the same principle that is used for the other connection properties also to the schema. Would be nice if this could be applied for netbeans 7. Greetings Matthias
> Proposed patch (see comment) Thanks for your patch again. > Would be nice if this could be applied for netbeans 7. It couldn't. 7.0 has been in high resistance mode, only FCS stoppers can be fixed - http://wiki.netbeans.org/NB70HighResistance
Matthias, the patch doesn't work correctly. Connection's Display Name nor default schema (visualized by bold font) doesn't reflect this change. Needed to propagate this change to other features. Nice to have a property customizer for choosing from existing schemas only.
Created attachment 108236 [details] Schema Highlighting before change
Created attachment 108237 [details] Schema Highlighting after change
(In reply to comment #2) > Matthias, the patch doesn't work correctly. Connection's Display Name nor > default schema (visualized by bold font) doesn't reflect this change. To the highlighting please see screenshots - this works as expected. But then I just realise, that there is some strange interaction going on. There are somethinks in this module seem strange - for the record: A change in the jdbc URL is also not reflected in the node. But this is wrong, but I headed in the wrong directions in the inner workings of this module. I have to take a closer look.
I observed the wrong behavior with Java DB - default connection to APP schema. After change to SYS schema, no change in schema highlighting.
Created attachment 108380 [details] Updated patch The updated patch adjusts the connection node so that changes in the username, database and schema are correctly reflected (these 3 properties indirectly influence name und displayname of the node/connection). The displayname and name is only set, if the new name is not the same as the old or the autogenerated one.
Thanks, the patch2 makes it better, but I still see a problem while editing SQL commands in editor. At least, Code Completion doesn't change the default tables (tables don't requiring schema prefix) if the schema has been changed. IMHO it's not ready for apply now.
Created attachment 108572 [details] Patch Version 3 Ok - if I continue this I will have touched each part of the database explorer api ;-) The problem lied in the fact that the Metadata for a database connection (handled in MetadataModelManager) was cached and as the key was the connection itself the meta was not rebuild when the connection changed. In the connection node is a function that updated the internal metadata of the connection and now also updates the MetadataModelManager. Additionally this fixes the case where the default schema was changed via the explorer view and the syntax completion did not follow this change.
Could you please give it another spin?
Hey, this is targeted for 7.1 - will it make it in? What holds it back? What can I do?
Thanks, this patch should work properly. Integrated in core-main/rev/9d6a9e2e7ec1
Integrated into 'main-golden' Changeset: http://hg.netbeans.org/main-golden/rev/9d6a9e2e7ec1 User: Jiri Rechtacek <jrechtacek@netbeans.org> Log: #197105: The schema-property should be editable in unconnected state; applied matthias42's patch, thanks
*** Bug 150215 has been marked as a duplicate of this bug. ***
*** Bug 191359 has been marked as a duplicate of this bug. ***
*** Bug 163073 has been marked as a duplicate of this bug. ***