Potential Database Features for NetBeans.Next

These is a list of fdatabase eatures under consideration for inclusion in future releases of NetBeans. Iteams are merged from a few separate sources. Thanks to Andrei for providing some initial ideas.

1. Merge SQL Editor and Query Editor into a single Editor

• Have visual pane expand/collapse on demand ?

2. Support JPQL as well as SQL in the SQL Editors

3. Code completion in the SQL Editors

• Big usability issue. Many requests for this one.

4. Drag/Drop support for JPA Entity Beans in Visual Web apps (John)

• 94188

5. Support for development with disconnected databases

• Requires metadata caching

6. Read-only E-R diagram. Visually displays the tables and relationships in a given connection.

• Some stuff already exists here, but not linked in.

7. Database schema development.

• Big thing, not really well thought out yet. It should do what the current Create Table / Add Column dialogs do and more, like support foreign keys, have a more user-friendly UI, perhaps also have an E-R modeller.

8. More user-friendly dialogs for adding a new connection and connecting an existing one.

• See http://www.netbeans.org/issues/show_bug.cgi?id=68991

9. Add a file template for SQL files

• Invoke File - New File, select Databases, select SQL file, a new SQL file is created and opened in the SQL editor

10. History in the SQL editor.

• Not trivial, since the editor can now execute scripts, so it is not clear what to put in the history (all executed statements?). Ideas on this welcome.

11. Editable SQL execution result.

• When you execute a SELECT statement in the SQL editor a read-only table with the results is displayed. It would be nice to allow editing and adding data in that table.

12. Other Entity-Relationship Diagram features ?

13. Other minor enhancements

14. Create visualweb page from JPA Entity Class (John)

• I don't want to reproduce the list here. There are 126 open issues of type Enhancement or Feature filed against db, and 33 filed against visualweb/databases and visualweb/databinding. Some of these are already called out above. Offline we can review these detailed lists and identify a few high-priority items that we want to break out separately.