2008 Database Survey Comments

This list is from the question asking for further suggestions. Good reading! You'll see some themes...

My SurveysAddress BookFAQUpgrade Subscription

Please let us know what other features you would feel are very important for a database tool for developers, or any other comments you may have

Complete list of all responses given to this question

  • database that will configure registry and interfacing port of any programmable rom
  • I want everything,I can do in Sql Server 2005 visually.
  • edit more like Eclipse in display javaAPI
  • I would recommend integration with db4O, an true OO Db. The db4O team has done some very good work with transaction concurrency to make web apps more robust. I am in the process of completing a Java*db4O application. Unfortunately, I don't have any load tests to provide you at this time.
  • code completion for sql tables, fields, stored procedures

support for stored procedures code highlighting and syntax highlighting visual indication when a variable used is not defined inside a stored procedure

  • c#
  • support open frame eg:hibernate,

generate pojo from table

  • cross*generation and synchronization of E/R diagram with UML Class Diagram.
  • Please change the survey so: language (Ruby, Java) is used rather than a Web*Framework (Ruby on Rails, Struts).
  • a set of 'middleware' classes which implement communication between ui controls and database contents
  • code completion for SQL editor;

visual schema editor and table creation; databse tool to be extensible so developers can add support for specific sql dialect (data types, constraint creation, etc).

  • possibility to change password, location, and users/managers for database access.

possibility to change storage location.

  • User of PostgreSQL. Tools for manipulating data in a database or the database itself aren't very important for me to have in NetBeans since the tools with my database are good enough (schema/table view/modification, simple SQL generation, data import/export). But Java/DB intergration tools would be very welcome (Which I'm actually working on in my spare time, but it's slow going.)

Visual tools for query creation isn't very useful to me, but getting information on a written query (execution plans, column datatypes etc...) at the hover of a mouse or click of a button is. (then again, I'm a poweruser in this area) See also Eclipse and IBM pureQuery.

  • I'd like to be able to change the font used inside the SQL windows. I need a fixed width font!
  • VWP * Please fix CachedRowSet query SQL in SessionBean so that it can be on multiple lines.
  • More power NetBeans experts council (and of course, the DB Team).

I believe we could include some more object*oriented event*driven RDBMS functionalities in NetBeans, particularly (we still maintain) Paradox and Oracle development integration (import|export). Thanks.

  • I am more interested in JPA (or Hibernate) query language support. Query generation and testing.
  • start with a sql statement and

build a code generator, using the database metadata for a record to contain / insert/update data into the table

  • build a tool to build the prepared statement SELECT for the sql code
  • support pl/sql in oracle

I have a crude tool to start with if you're interested mdever2000@comcast.net

  • 1. Code completion on available SQL and schemas in SQL Editor

2. Hot*key SQL execution 3. Ability to edit queried data in place (use view data and edit the cells) 4. More ready to go database drivers 5. Paging execution for result sets over (N). Previous and next buttons around the table view of data that can retrieve the next query size of data or view a previous one

  • Query profiling and optimization assistance, to whatever extent is possible in DB independent way. Also, it would be great to have an automated tool to generate large amounts of (pseudo) random data for testing purposes.
  • I always have a problem try to create a new connection when using a different directories than the defaults
  • * export of db data to sql insert statements
  • ability to view and delete all constraints related to table
  • smart deletion of tables that analyses constraint dependencies and drop constraints in the right order.
  • crud for constraints

In general as much functionality as possible to allow me to do the most basic DBA type activities without having to use another tool.

  • I'm sure this isn't the place (I'm thinking UI would be), but it would be very very nice to be able to create keymaps to db commands such as rails db:migrate
  • Referentiell Integrity
  • Schema and data comparison. The ability to sync between 2 databases (ex. production vs. development). There's a huge need for this that currently only commercial vendors are fulfilling. Having an open*source alternative to do this would be great.
  • thanks for such rich tool
  • A good support for E/R diagram and Schema manipulation
  • reporting tool
  • most developers use some sort of ORM nowadays so the ability to integrate with popular ORMs is way critical
  • make it easy to mashup (use) java inside dot net. I want to switch to java but it seems to hard. So make it so I can do pieces. also do something like birt but using netbeans
  • Nicely formatted SQL statements when printed to System.Out, or System.Err.

Currently unless I go through and place \n in the sql statement any errors are very hard to debug. It would be nice if netbeans formatted the sql with new lines in the appropriate positions. Need the ability to copy and paste from the SQL query tool directly into code (ie convert it to a well formated string) The sql query tool should be able to set the parameters within a sql so that you can test prepared statements easily.

  • database schema visual diagram tool, just like UML tools only for database
  • its good soft
  • Integrated with the popular DB connection pool tools
  • Able to reverse engineer db schemas to E*R diagrams
  • Something similar to Rational Data Architect
  • Generating the CRUD application as a starting point from one to many linked tables, not just one. Don't forget "Mixed Case" table and column names (nicer and can save a lot of time, if they work)
  • FirebirdSQL support (if not already available) * this is an Open Source embeddable RDBMS that is excellent for desktop apps.
  • I dont know if it is posible to have a JVM running without operinting system, just for development. When I run just winXP before I ruan netBeans it takes like 500MB of RAM..!
  • code completition, data base vendor support, e.g. packages in oracle databases
  • Tighter integration with ActiveRecord (from Ruby on Rails)
  • data manipulation and import/export features
  • Reverse and forward engineering is key.

I also hate that many tools automatically format certain types of data the way somebody thinks is preferable. Date values, for instance. I should see them in the format native to that particular database. For instance, JDev (I know that's not you) displays dates in a MM/DD/YYYY format for MySql and Oracle. MySql's date format is YYYY*MM*DD and Oracle's is DD*MON*YYYY. I guess it could be the client drivers that I'm using. Anyway, makes it a real pain to translate valid date values from one and insert it into another. I have to bring up the native command line clients on both the Oracle and MySql instance to determine how to proceed.

Also, I'm really not a fan of query rewriting by client tools. If the Oracle optimizer does it internally, fine. But if I define a query in Netbeans only to pull the text of the query 2 seconds later, the text should be the same. Please stop designing tools that assume that developers don't know code level. "Declarative development" can be useful, but I much prefer to code it myself in many cases. DBA's use many, many scripts. Don't over automate.

Thanks for all you've done.

  • generate export data in INSERT SQL Statement.

generate DDL script of tables

  • My SQL
  • I'm never going to use NetBeans to build my database I'm going to use a database*specific tool or command*line alternatives. But easy integration for *reading* databases is a huge convenience, and leveraging JDBC right into the IDE has been a great feature. I'd love to see the ability to store and execute parameterized queries, the way we execute PreparedStatements in code maybe even storing them in IDE*recognized files (the same way we can store .ics files from that Task List module and open them "natively" in the IDE.)
  • Here are some features I think would be of tremendous help when using the db tools in NB:

1. Stronger SQL query editor that supports multiple queries and ability to run selected query in the editor. 2. There should be an indication of how many rows were returned from a result set. 3. Number of result rows to display should be configurable and should default to 0 i.e. display all rows. 4. Ability to save queries in the editor to a text file and re*open such files in the editor. 5. Option to display results from multiple queries in same or multiple tabs. 6. Option to log queries to a local file with timestamp. 7. Transact*SQL support.

  • Retrieve as needed data view table grid, ie retrieve n records and retrieve next n records when scroll down.
  • Tight integration between the visual query tools and the rest of the frameworks.
  • simple, responsive UI
  • I cannot stress how much of a benefit it would be from an architectural standpoint to have a tool that produces an E/R diagram of some sort (Chen, Information Engineering, UML, etc.) that would allow us to produce DDL by visually modifying tables like Rational Rose and also reverse engineer visual depictions of tables from existing databases. If that was possible along with database schema change management for the DDL it would be a big win for NetBeans.
  • Developing Stored procedures and be able to debug them ist critical!!
  • * implement standard SQL
  • good documentation
  • Stanadr data binding framework to make database*GUI development easier and faster.
  • Data binding Swing components
  • database schema structure changes with minimal data losses...
  • Wizard to create a server side application with a database and in addition classes for client applications, able to cache database data and synchronize back using web services and jnlp persistence. optionally exchanging data with other peer using jxta would be very very fine.
  • * Visual database modelling in an UML*style syntax (as an alternative to E/R modelling). While E/R is (IMO) a great method for analysis and creating data models on a relativ high abstraction level, modelling in an UML*style syntax has some advantages when I need to model details that are more specific to SQL databases in general, e.g. contraints, triggers etc. Interoperability between E/R models and UML models would be great!!!
  • Often it makes sense to work with users, roles an permissions on database level (although with app. servers this might be a little bit old fashioned * at least I see many approaches that use always the same db user to connect to the db, and the app server users and permissions are implemented only on app server level). Up to now I have seen no visual db modelling tool that shows PERMISSIONS in its diagrams * or even allows to model permissions. That would be a great feature.
  • With network load an transactions in mind it makes sense to pull down as much business logic into the database as the business model alows. As long as logic concerns data and permissions, triggers (and some other sql features ...) are (in many cases) great means to implement business logic. Unfortunately E/R and UML*style diagrams offer no means to describe trigger actions (AFAIK, but maybe I missed something). I could imagine a notation for triggers on a table in the same manner like operations of a class in UML OO modelling. For a more database*centric design this would be an invaluable improvement.
  • Take a hint from Borland's VCL about data binding. Or even for fixing Swing for that matter :*). It is simple and effortless.
  • Already stated, but in place query editing for SQL in code would be super handy.
  • Converting tables/schema from one db to another.
  • Design*/Compile*time Database View.
  • Database table editing. What I mean is the ability to browse the contents of a table and modify the contents. This is very valuable for testing or initial data creation. Sure there are database utilities for this, but if I don't have to leave my IDE to do it this way.
  • Comparing databases schemas for major database management systems.
  • Ability to copy a large amount of data that is the result of some query into the clipboard.
  • Templatetising the creation of StoredProcs for the basic INSERT,UPDATE,DEL for a table.
  • Something that would allow JPQL testing with either graphical or textual representations of the object values being returned.
  • just full fill the ones above
  • just full fill the ones above
  • diagram > orm
  • I would like to have the option to integrate tooling like dbUnit with the database tooling.

Also it would be nice to have a default query linked to a double*click on a table, which would be executed instead of the current default behavior.

  • *report generator
  • auto relation
  • admin tools(backup,recovery)
  • blob,clob data type displaying
  • expand matisse (swing gui) to make connections to database fields visually * similar to VBA. Drag fields from DB to matisse and use the field names as labels. Enable field checks of data type based on database data type (numeric, date, text etc). In summary * use the info contained in the schema when making a form from data in a database.
  • *Export data in SQL INSERT format
  • "Extended" schema exploration and modification * functions, procedures, triggers, etc.
  • Mixing database tools with ORM technologies (especially JPA).
  • Import data from XML file.

On windows, import data though ODBC and import and export data from/to xls file(Excel files...)

  • auto*completion for table's names and attributes.
  • profiling
  • SQL "worksheet" allowing grid/single*record editing of any legal, editable query (ala Benthic Software). That is, the ability to query with joins and/or updatable views and EDIT the results. A lot of my testing involves editing/manipulating data. This often needs to be done BEFORE I have created nice data entry apps.
  • More or less 'automatic' generation of connect strings, but editable, of course
  • In reviewing briefly the use cases found here:


I would argue that Ruby/Rails developers do need to interact with the database alot. At least initially, the schema must be defined ... yes this can be done using Migrations, but even still a valid db user/pass must be setup. So, if Netbeans can get the CRUD table methods setup then Ruby (and even PHP) based users could easily interact with the database schema to make quick changes.

I currently am migrating data between databases, I'd hope that Netbeans could help to facilitate this with allowing a db connection instance to select other databases that user is valid for and to allow table aliasing to save my typing even more that autocompleting.

  • An equivalent of the MS Access query designer.
  • Integrate Netbeans with Oracle 10g database
  • It seems the connections time out way too quickly. It gets annoying to go expand a table only to find out that you've waited too long and must reconnect to the database.
  • Support for cross*platform database operations. We are working on software that needs to run against Oracle and replicate data to mobile PCs running SQL Server. It would be nice to be able to do things like compare databases from different platforms and generate scripts and queries for the different platforms.
  • 1. An add*on that checks whether the SQL statements are "standard" or database*specific (for instance SQL 3 / SQL 2003, etc.) so we can actually try to write database*independent queries

2. Automatic code generation for database connection (*> connection pool "factory") based on chosen lib.

  • I use Oracle SQL Developer and Oracle JDeveloper a lot. These tools provide excellent support for Oracle databases. Some of these features, like an SQL query tool with code completion, would be very nice to have in NetBeans, especially for other databases like MySQL and PostgreSQL.
  • 1. Ability to view any schema in the database.

2. View sequences and constranits.

Keep on improving the NetBeans*IDE. I would use it rather than Eclipse for new projects, because it is easier to use.

  • Essentially I'd like aquafold.com's Aqua Data Studio (which at least at one time used the Netbeans editor components), but integrated into the Netbeans IDE. So, basically, whatever you can to do make Netbeans' database support more like that. Given the rapid progress they've been making recently, especially for stored procedure debugging, you've got a lot of catching up to do...
  • I work with oracle mostly, so I would like to have support for some oracle specific features, like explain query execution plan, browse/modify sources of views, stored_procedures, tables, sequences etc. It would be also nice to have some kind of 'sql pretty print' as offen the queries are inlined in Java in not very readable form (one line or chunks of strings with '+')
  • JSR 296 is very important for us

JSR 295 and JSR 296 for: SQL*RDBMS*Query * Master*Table * Detail*Masks are the very thing we need actualy in a CRUD manner

  • store procedure test environment
  • 1.just like Ruby ,Rail or others languages support

2.GUI programming and IDE restriction

  • CRUD DAO generation from Schema for non*JPA/Java EE 1.4 projects
  • Something like HeidiSQL would be very nice
  • database procedure editing
  • In*place query*editing & testing of JPA code.
  • Explain Plans and Query Cost Estimates
  • drivers that are not dependent on the underlying database * like JDBC_ODBC bridge or Hibernate.
  • I currently use phpmyadmin for most database tasks because the IDE interfaces all seem lacking compared to this web UI.
  • There are already so many database tools that have the features mentioned above * as a developer I am far more interested in development tools that enable me to link gui with data i.e. the ability to easily set up persistence choose which model/attribute(s) to display in a control including a simple ways to set up comboboxes and editable grids. I really think more concentration should be placed on those features for netbeans rather than reinventing the wheel (so to speak) of creating yet another tool that allows me to manage and query my database. Yes I know a start has been made but till now attempting to bind combo boxes to data just results in code that will not even compile, there is no easy way to use a combobox control in a table column. I shouldn't have to write dozens of error prone lines of code to enable binding.
  • easy object mapping and code generation
  • sql auto*completation while writing, including database objects (tables, store procedures, etc)
  • no idea now.
  • Templates for generating users and passwords and logins

Templates for audit*trails

  • I have a straight odbc connection to the db for Ruby on Rails using Ruby*dbi and the ADO.rb. PITA I know but it's the project. I just want to be able to mimic some of the basic functionality in enterprise manager from a window in NetBeans. See the tables, the column defs and rows in a table. An interactive sql window would be gravy. I can use the console for that tho especially since we use ActiveRecord. But what a breath of fresh air it would be not to have to open the EM for all that.
  • CRUD wizard for web applications based on JSF and EJB 3
  • would be nice to have a free text ejbql query tool, so that you can write/test ejbql queries at design time
  • I would like the ability for NetBeans to create entity tables from database views (Oracle). Currently, NetBeans will only generate entity classes from database tables.
  • 1. SQL Editor code completion

2. Ability to view (more important) and edit (less important) database functions, stored procedures, and packages. 3. Ability to browse database schemas. (Note: I use the free Oracle SQL Developer a lot and would like to see some of those features incorporated into NetBeans)

  • Code completion when writing sql queries
  • it should have report generation as well.
  • * Visual E*R with edit functionality
  • databaseschema versioning option: when changing the E*R diagram assign a version to it and store the changes as alter statements that can be run later on an old schema. This way database migrations become easier
  • Hibernate support

Might be superflous with EJB3, but lots of people are using it.

  • Database explorer: not knowing the exact details of a JDBC connection, but be able to browse all databases/schemas for a given DB server.
  • Support for creation of CB2 Datasources and use of JNDI
  • 1. a very simple to use database explorer like that of jbuilder more or less.

2. CRUD for header and detail that works with a nice tutorials.

  • 1)Using schema and table definition the tool can create a "crud" table/page*form automatically.

2) Db independent programmi

  • The ability to set up custom field or table properties such as IDENTITY or AUTO_INCREMENT and associate them with a driver.
  • support for GORM (Groovy's OR*Mapper).

and better Groovy/Grails support.

  • Export data using INSERT statements
  • Import data from a XML file

JPA 'drag and drop' (or "next, next, finish") mapping

  • Export DB schema ax XML Schema (To use e. g. with export to XML file.

Import data from XML file.

  • To run the selected code only (in selected) would be great, also a shortcut for the 'run query' button.

Keep up the good work guys (:

  • Query Builder like Visual Studio
  • tools for developing stored procedure
  • Stored Procedures Programming (like PL/SQL for Oracle Databases) and Debugging
  • Best tool is toll like IBExpert for Firebird,


  • The table modification and query features of SQL Server (and Access) are a good point of reference.
  • 1) Export to JSON format, 2) Cross schema query builder at present you can only work in the current schema.
  • The ability to drag and drop code on a form and have the correct controls displayed or easily changed. Let's say for numbers the spin , for foreign keys lets say a dropdownlist with a field i will fill. checkboxes for bools etc
  • Integration with Hibernate/JPA. For example the possibility to query through HQL/JPA QL.
  • Query "object" in the style of visual studio.net (if you like, a visual version of the "Prepared Statement")
  • more deep HIBERNATE api integration
  • I use aquafold datastudio:

http://www.aquafold.com/ it's great 4 my jobs of vertical web*developer (from table to html). It would be nice if Netbeans.....something like!

  • schema completion (as in the squirrel sql, which is based on netbeans ;), plugins for dbrms to get to their specific features (view definitions, packages, etc)
  • O/R mapping facilities (Hibernate for example)
  • i use navicat (http://www.navicat.com) and toad for mysql (http://www.toadsoft.com/toadmysqlbeta.html). they have lots of useful features. please have a look. for more java*centric db tasks, i'd love if there were good tools for jpa and hibernate.
  • Take a look at dbwrench they have some rely nice features.
  • SQL Query Optimizer
  • Graphical database creation & handling tables, query etc. more sophistically like Visual C# IDE.
  • Import/Export between different DBs * see DBVisualizer (http://www.minq.se/products/dbvis/) for a very good implementation of a general java*based db tool * excellent!
  • Stored procedure metadata exploration, automatic generation of stored procedure call wrapper classes, similar to Generate Entity Classes from Database.
  • ok
  • "UC*S5 * Quick and easy way to create tables, indexes and views" is important. Why else use Netbeans with a database? The current Database Desktop App wizard is geared towards views of a single table. Would like any easy way to make a desktop app looking at an entire database. E.g., select tables from a tree on left hand side of window, which then shows the table view on right hand side of window.
  • Although I have marked some features above as nice to have I am happy to continue using OpenOffice Base to implement them. Perhaps providing an easy transition between the two programs would be preferable.
  • Main feature needed are covered by survey.

Oracle pl/sql and sql validation would be a nice to have

  • Ability to write and compile database procedures/functions/packages, e.g. for Oracle Database, recognises PL/SQL syntax.
  • Support for object oriented databases. Support for "visual" rule based query of dB.
  • Flexible File Encoding Settings; More Shortcut keys; More Beautiful Look&Feel.
  • based on user selection of tables and fields some basic and automatic code generator for CRUDE operations ( ALTER, INSERT, DELETE ) following some patterns or framework
  •  %100 MS SQL Support
  •  %100 MS SQL Support
  • multiple result sets. We use Sybase as our database so database functions like sp_help will not display.

I think this issue is two part :* 1) stored procedures need to be able to be fired off as a query ( not executed) 2) Many stored produces multiple result sets, which I don't think is supported ( haven't got pass step one)

  • As per AquaData Studio it's very handy to have the ability to set parameters such as logging level and compatibility level etc * DBMS specific features made available via the JDBC driver in use.
  • i´t would be good to have the ability of change table's data without making an UPDATE query, just like QUEST TOAD
  • none
  • I very much like to see support for db4o.

See: www.db4o.com

  • I would like ant tasks that would test whether the modified time in the database for a stored procedure was out of date compared to the source file and update the procedure in the database from the source file if necessary.

I would like to see a 'relational database' project template that let you modify schema and stored procedures with tools to import and export data from tables.

  • FYI, I use SQL Developer for Oracle regularly as well. So a similar feature set to that would be great.

Pretty much any/all of section 6 would be fantastic and much appreciated.

Also, on another topic, double*clicking to select words is really clunky since the editor seems to have trouble detecting the caret is over a word or something. Anyway, I do that a lot and it's rather frustrating to not select the word.

Also, double*clicking on tree*views frequently results in editing the name of the node, which is generally not the desired result (for me). I would like to select the node. I would in fact, not mind if you had to choose "rename" from a popup menu and were not able to rename a node by double*clicking on it.

  • simple handling with the most databases
  • I would like to have SUN develop a standalone database like Microsoft Access that we can put anyware on the system and write a connection string to. This stand*alone database would function like a SQL Server database, with stored procedures and views, but be file based so we can deploy without having to install a program like SQL Sever Express.
  • I want everything that DbVisualizer has.


  • Transfer from DataBase to other DataBase
  • Look to Foxpro's seek(),scan,cursors,data manipulation and othe database commands
  • to let the netbeans act as if it's an interface tool with full functionality
  • Jav DB Will Aprovement
  • Import data from a XML schema file.
  • would love to have an ER diagram designer and able to generate tables from the diagrams
  • none
  • 1)inbuilt embeded server

2)It is very boaring to write Connection statements to connect databse.Want a full feature server which is friendly to all(sql,oracle,MSAccess,excle etc.,etc.) database access and if we want to access these datafiles, don't need to write code. Just drag and drop should be the best option. (Plz do some thing like that!!!).

  • As well as MySQL and PostGree Bundled drivers, I'd like to see Firebird JayBird driver included, for it's the best !
  • In line editing query results
  • It should be as easy as .NET
  • simple template engine for pojo/java beans generation from sql query
  • database programming: functions and procedures
  • multple windows for each database/problem
  • db tuning and performance visualization
  • In*place query*editing for JPQL embedded in code

In*place query*testing for JPQL embedded in code

  • Fix issue 49994. NetBeans db functionality with Oracle is almost useless otherwise!
  • It's important to distinguish actual references from implicit references, in which the value of a field usually but not always reflects an identifier from another table. If this could be managed more effectively, it would be of great benefit.
  • For sql files used to create triggers, tables, etc., it would be nice to have CVS integration to place in source control. Also, would be nice to "grab" table structure and view as text.
  • Having the embedded JavaDB is great for being able to try out demos and prototyping quickly and easily.
  • JPA/UML instead of E/R diagram.

Mapping DB x JPA Entities like Dali.

  • sql code completion
  • PL/SQL support.
  • PS

I hadn't used Netbeans for a few years, so I don't know all database related tools, that it's new versions provided. My answers based on common practice with Java IDEs.

Thanks, Andrew

  • Adding support for JPA in the IDE like tools for generating DB schema from annotations.
  • please provide database modeling tool too similar to 1 available in jdeveloper
  • Since you are not specifically listing Django or Cake or Struts, why not just list Ruby? Rails is not a development language. Ruby is. Many Ruby developers are building production applications in Ruby using Nitro, Ramaze, Merb, Iowa, and other Ruby frameworks. Please do not assume Rails is all there is.
  • support stored procedure
  • It's very important to have a visual data tool in IDE permitting developers interact with database without using third party visual tools.
  • query completion of tables, columns, etc.
  • First class support for PostgreSQL should be a very high priority. It is the *ONLY* truly free, no*strings*attached enterprise*quality DBMS.
  • code generation ddl2java ddl2hibernate ddl2jdo
  • 1.A GUI for forms and reporting.

2.data grid that can be used for entering data and data grid for analyzing data (like ExpressQuantumGrid and ExpressPivotGrid from www.devexpress.com) 3.A reporting and graphics tool integrated in the IDE (maybe JasperReports). 4.More appealing controls, SWING is obsolete.

Dont't make the IDE good for everything, just concentrate on some areas. Make it simple to be used.

  • not specific to any special database product
  • Hibernate/JPA aware editing is important to me.
  • support for creating primary keys with autoincrement
  • A good database tool should:
  • have an excellent SQL editor, with editing history, highlihting, no encoding problems
  • allow access to table contents and allow changing them
  • allow inspection of dependencies

A great tool should:

  • easily generate DDL or SQL representing objects (views, tables, procedures) in the database or database content, display the DDL for any GUI made change before the change is applied
  • allow basic model visualization (pan, zoom, add table/remove table from diagram)
  • be fast
  • support dozens of databases
  • be able to compare differences between two versions of a database
  • JPA entity mapping, class to db visually, switch betweeen UML like class modelling and ER style, mixing class diagrams with entity relationship diagrams
  • a connection management library and template for accessing to different Database engine in network easily.

for example a library with getDataSource function that can be configured with UI in netbeans. so developers can test their code with their DB easily.

  • SQL Intellisense, autocompleting database names, fields, sql commands, ... Like in Aqua Data Studio, It's very nice tool. That would be satisfying.
  • decent code completetion when editing sql, for example the ability to understand table alias's.
  • 1.Analyzing the existing Database schema and generating ORM code(e.g hibernate mappings and DAO interfaces & classes) and vis versa would be great. Build time ORM*DB schema verification tool set that can be incorporated into build scripts like Ant/Maven.

2. Report generation capability by providing basic customizable WYSIWYG report templates by generating template engine*Database bridge code.

3. Schema modification/refactoring tool set to help implement I18N capability in preexisting database to allow multiple language 'data' storage within same database. 4. Performance/UI Responsiveness when using Query Browser.

Disclaimer: I am no longer core programmer. Wish list mentioned above is based on day*to*day project needs that we come across as IT service providers.May be some of the features are already available in NetBeans that I am not aware of.

  • 1) Visual tools for rapid forms and report development (just like microsoft access)
  • Store procedure/Trigger support
  • configuration for e.g. Informix to use ANSI SQL
  • With regards to Read*only E/R diagrams these should model "Rials" relationships, that is based in field names and not foreign keys
  • Better sql history buffer. Perhaps persistent between invocations of netbeans. Sometimes it takes quite a

few tries to get a query right. I use the database tool quite a lot with HSQL, Derby, and Postgresql. One small frustrating thing is you can't see the query that makes up a view. This may be a JDBC issue. Another nice feature would be to support whateverr "explain plan" mechanisim exists. This is database dependent though, which makes it harder. Still, it would be nice to make sure that indexes will get used, especially on large databases where a table scan takes an hour.

  • An SQL Text editor/tool that matches the featrues of the database dead on. For instance if I need a boolean field but I'm connected to a MS*SQL database it will anticipate that I need a NOT NULL bit field. By the way you all have done a very nice job with Netbeans. I can't imagine using any thing else.
  • Having a read/write ER diagram would be awesome. I haven't found any tool that does a good job of that. Solid data manipulation tools though (look at table data, edit values) and SQL file import/export are really essential.
  • visual relationships between tables
  • Dear Sir

the ability to debug the stored procedures and functions is a must. I would like to have a sql developer from oracle like tool plugged into netbeans

  • I'd like to generate XSD schema from a queries resultset (including data typing)
  • Allow third parties to integrate specific DB management into the default NB DB modules (manage oracle for instance)
  • Connections to other database types, such as sqllite3; built in support for database drivers rather than having to install and point to each one (or plugin support for same); the ability to easily query and work with the database while also working with source files.
  • * Never ask the user whether (s)he wants to see all records (see PL/SQL Developer or DbVisualizer for better solutions)
  • Give database connections symbolic names instead of hard*coding the connection URL
  • Make the database module good enough for small to medium*sized database queries
  • Better support for Oracle (for instance, showing table structure by using the user_columns and other Oracle*specific tables instead of just the JDBC API because the Oracle JDBC driver calls analyze otherwise, which leads to priviledge errors in many db configurations.
  • The RadRails IDE had a nice data*grid view of table contents that allowed editing/inserting/deleting row data... could be handy. Also, please consider Ruby Projects using the ActiveRecord gem but outside of a Rails web application for feature support.
  • Ability to create initial database for common DBMS, like mysql and postgres. Helpful for green*field Rails development.
  • Testing tools like DbUnit
  • I know this is the database survey, but the #1 thing from Netbeans that I want for PHP is Matisse GUI Builder (I believe it has a different name now).

I was glad to see your post on the PHP*DB list.

At least export Matisse GUI to HTML; perhaps Javascript/Ajax to execute dynamic layout rules.

I was a little surprised that this survey is in ASP.

Maybe look at tersus.com for how they handle DB modeling? Basically I want a tool that helps my work, but not as good as Tersus where I may feel I could easily be replaced LOL. Tibco almost maintains such a balance, but I haven't seen any security for the underlying app yet.

I primarily use phpMyAdmin to manage MySQL DB's. I've used fabforce dbdesigner to get a graphic view of tables to print out, but manually drew the relations (I believe that was because MySQL didn't support referential integrity at version 3 and 4, but my company is almost on v5.)

Maybe a built*in query*log view (with various filters)? I need to go to a shell now for that.

I sometimes export to xls for some users.

Maybe some kind of performance metrics (slow query log?).

Warnings for SQL injection attacks for production queries? Maybe a simple test*type query is not warned, but when intending to deploy to production, hints or warnings could be offered?

Thanks for considering PHP developers!!! I've used Netbeans to beautify indentation for C/C++ and I think PHP code, in the past. Netbeans refactoring and integrated UML is awesome (but I have seen a slowdown in responsiveness as the project grows).

Netbeans Matisse GUI Builder + Tersus (with maybe a pure UML import/export Tersus doesn't use UML but can import the HTML GUI) would be the best development environment I could think of.


  • PL/SQL syntax highlighting would be great
  • Too amateur to know whats there and what would be nice.
  • 3 tier features and some actual database features for web ported to desktop applications.
  • Viewing and editing plsql, stored procedure

for oracle. Generating jpa code with NetBeans is ok. But for everything else I have to use Toad or a similar tool

  • Support for ORM (see visual paradigm)
  • Some nice to have's:

Multiselect drag and drop of fields from schema into query editor.

Rightclick describe object, table (fields/types/sizes) or field (type, size) at cursor. No need to navigate to table in schema.

  • Embed squirrel sql into netbeans
  • I think that it would be very nice if we could have debugger integration, so if there's SQL embedded code, we could debug it as well. And if I can get picky, I guess that code completion would be very, very, very nice! (:
  • Maybe support or integrate with JPA
  • Visual schema exploration and data exploration.

EJB*QL Query Designer/Wizard whould be nice

  • migrating data to and from different databases
  • object persistance (like JPA) and binding simplification
  • I use JPA in all my projects, so I'm more interested in tools that works with JPA and EJBQL rather than SQL.
  • Full generation of backing beans (JPA or vanilla jdbc) that works consistently.
  • complete DAO generator
  • * see SQL that makes up the VIEW
  • code completion in text*based query tool
  • Stored procedure editing/debugging.
  • My background is writing a *lot* of SQL embedded in C/C++, so that definitely moves my responses away from the visual editing of actual database schema and relationships. Just not that important to me as opposed to fast tools to export/import schema into a DB in a platform neutral way and help my code "match up" to the underlying schema as it matures. As the code evolves it becomes more of a challenge with the "do it all" tools to make sure runtime environments are actually in*sync with development.
  • Import and export data (load and extract) to/from *.txt file
  • Ability to debug a stored procedure or trigger
  • Database Schema Refactoring.
  • query auto completion
  • follow foreign keys. Klick and open a table to select the value of a field.
  • I'm very happy with it already. I use it constantly, especially with our AS/400s (a.k.a. IBM iSeries).
  • Making sure that tool works with all the popular databases

Java DB, Oracle, DB2, Sybase, MySQL, Postgress, Ms SQL Server and jdbc drivers Java DB: Apache , Oracle: think, oci, WebLogic DB2: IBM, WebLogic Sybase: various version of sybase drivers (jconnect 1...n), WebLogic Driver,) Other popular third part drivers.

  • support for the very simple but ubiquitous access, dbase, foxpro databases. These are still widely used but do not support a lot of features.
  • Working on Views, Store proc.
  • O/R mapping

Please look at Apple's EOModeler * although it is 10 years old, it's still WAY ahead of the pack in terms of creating object for relational databases!

  • feel free to refer Oracle SQL developer
  • I'm trying to migrate a mature database application from Oracle's old character based front end (SQL*Forms) to * hopefully * something in Java. I've got 20 years experience in firing up SQL*Plus and working at the sql command prompt, so that's reflected in my answers above.

My application is split across two schemas. It serves two business entities that share some information. Being able to easily work across schemas would be a plus.

I do see NetBeans maturing as tool for database development. I do find that improvements are coming rapidly. I'm just never sure what the best approach is to take as a designer. I can't sart working on porting an app over just to have the "best" way change in the middle of doing it, and leaving me with having to rewrite the previous work, or live with maintaining similar forms written with different styles/tools. I guess what I'm looking for is a "best way" direction forecast! I just got comfortable with RowSet implmentation as JavaBeanObjects and fleshing out that style of GUI form building, and the NetBeans 6.0 database application template seems to go in a different direction. I have yet to really figure out how they relate to each other, and how I can take the wizard*generated interface and make it into something I could give to my clients to use. It's great for seeing what's in a table, and manipulating the data. I'm curious to see how it extends to multi*table master*detail relationships, and how the user experience gets rounded out with little touches like prompting if you're about to discard unsaved changes, and how awkward it is to enter multiple rows in a transaction. Those are features I'd really love to see. There are ways to do that now. It comes down to maintenance effort and style continuity where you can make a basic assumption that the way a task would be coded in 2008 is pretty much the way it was coded in 2007.

Thanks for listening.

  • . or , in numbers
  • 1. SQL syntax highlighting and code completion.

2. An interesting feature would be hyperlinking through results based on foreign key relationships. Here is a scenario to consider, suppose a user issues a query and one of the columns is userId which contains id numbers associated with another table. If the schema defines this relationship as a foreign key the user should be able to double click a cell and execute the query that would view the record in a new or same editor, show the result in a tool tip or even click the cell and have the results show in a different pane. I've never seen this feature but it would be wicked cool and would ease the developer from having to issue tons of joins to see meaningful results. It could even be intelligent and detect mapping tables and automatically bypass the map for the developer showing the results of the map.

3. Provide the ability to store sql scripts in a file that can be revision controlled and opened easily.

4. Support for plSQl and pg_plSQL.

5. Variables and forms in SQL statements. Some SQL statements can be rather large and complicated however, changing some variables will show different results. Rather than hunting down the variables to change it would be neat if you can put a variable such as &customerId and when the query runs the variables will be presented in a dialog that the developer can fill out and run. This allows someone to define a complicated query that others can run and ensure then plug in the right values to find the correct data.

AquaData studio is a great tool for developers working with databases and is a good place to look for ideas. Furthurmore some database admin tools would be nice, for example, session managament for Oracle is important (See Aqua Data Studio's implementation), user administration, etc. AquaDataStudio also does number 5 above.

  • Generate SQL with visual tool with parameters.
  • export data to SQL insert statements
  • Mechanism for creating and working with a database for unit testing. Could be a feature integrated with the dbunit tool.
  • Hibernate auto generated code.
  • Ability to execute multi*line statements such as CREATE PROCEDURE
  • Include drivers for all major DBMS: MySQL, PostgreSQL, MS SQL Server, Oracle, DB2 by default.
  • Look at Visual Studio (C# express edition is free). Both 2005 AND 2008.

Don't make it confusing like Oracle JDeveloper.

  • Code completion when writing queries. Ability to highlight a single query statement in the query window and run via a keyboard shortcut. Ability to modify data in a results table and have it update the database.
  • I use the MySQL Query Browser for table creation and querying, and DBVisualizer (http://www.dbvisualizer.com/products/dbvis/) for looking at the diagrams of the databases.

Overall table schema creation and modification is very important for a developer, especially when using agile methods. Change happens often.

  • More JPA features like auto generating annotations for queries and auto update of entity classes/annotations when database schema is modified.
  • the database tool for netbeans 5.x is a very bad tool... is imconplete and is hard to use !
  • database design refactoring
  • We need a really good editor for SQL. Code completion is the most missed feature actually.
  • IDE integration for creation and maintenance of stored procedures and triggers written in Java
  • sql debug (stored procedures)
  • Right now, dearly missing the ability to load and save SQL snippets from/to file...
  • I think we might need some embedded analytic/mining features for intelligent apps
  • Better management of derby NetworkServer integrated in NB
  • Bookmarkable SQL statements
  • Performance suffers in NB.

Things are slow to do *> developer frustration *> change to other tool. I personally believe many of the problems are related to non*optimized code/algorithms, or "over*dynamic" / too eager solutions.

  • hibernate support

ibatis support jpa support

  • Frankly, I feel that JPA QL is just as important, or perhaps becoming as important, as SQL. The Hibernate Console in both Eclipse and IntelliJ is crucial to doing database*related work. I would like to see that as a first class citizen in the database tooling in NetBeans.
  • history of executed queries
  • In general most important is to have a rich public API for developers who build on the platform. Especially full access to the database explorer/ connectionmanager resources, creating and adding connections programatically, d&d, access to editors and query tools and the possibility to also access new features, like the ones mentioned in this survey.
  • Database engine management (starting, stopping, creating database, switching database, database encryption)
  • a decent SQL editor with autocompletion
  • E/R Modelling in a DBMS independent way would be awesome

I have already good tools to manipulate the data in my database. I don't see a reason why the IDE should provide this.

  • Although not related to the database tool, the database desktop application is a very useful template. Connecting that template with the database tool, so that you can modify the different events from the database desktop application would be a useful feature to have!!
  • display of execution plan of an SQL statement
  • Please just adapt SquirrelSQL as a NetBeans plugin and call it a day.
  • I used to be an MS SQL Server user. The visual query designer tools available in their Management Studio Express program is incredible. I've never used an other tool that helped me design SQL queries as good as this. It lets me choose any table, drag/drop any field to any field to create joins, let me visually describe left/right/inner join, etc. I can design any kind of query I want with it visually. The joins part is where I need help with (especially when there are many tables involved).


  • tsql scriptlets
  • For all of the questions, we would strongly prefer that you had been asking about JPA (Java Persistence Architecture) and the EJB 3 query language instead of raw SQL. We do very little work at the raw SQL level anymore. Instead it is JPA and/or Hibernate HQL.
  • Would like to convert to JavaDB but large app depends on Boolean data type. I do understand that this is not a Netbeans problem but maybe if enough request it some good may come.
  • Haven't used the old RDBMS for years, have been using OODBMS for all development. Would be nice to see something in NetBeans for these state*of*the*art dbms
  • Excellent Java Persistence API (JPA) support. Syntax highlighting for SQL.
  • The current tools assume that I'm the only person working on a project persistent unit classpaths get stored in my ~/.netbeans/5.5.1 for example. I'd rather see you invest time in getting the little details right before adding new stuff.

Why "export as XML" without "import from XML" ?

  • Something like DataGrid control in Microsoft's Visual Studio
  • Provide a visual database maintenance environment (similar to MS Access, and MS Visio) showing relationships between tables and allowing maintenance of all via the visual interface.
  • It would be nice to try to figure out if people are using database specific queries and help change them into Java's cross database syntax.
  • I'm very pleased to see NB including DB capabilities. I have not yet used them extensively but some day I will be on a new project and it will be quite important for productivity.
  • Support for the Firebird database. You can add it, but it would be nice to be on par with MySQL support. It is used a lot in Europe.
  • Something I think which would be more important than having in*place editing would be able to pull out SQL from Java, JSP, other code and quickly put it into what ever SQL editor the user chooses. It would also be important to be able to come the other way or paste from plain SQL text into the source file and it be formatted into a string for what ever type source it is. It would operate based on the clipboard.

I think the in place editing would be really nice to have as well as it would make things more productive, but may be something which would take longer to get working correctly unless it has already been worked out. I think copying and pasting code would be faster to put in place, and I think also if the SQL editor to be used will be NetBeans then there could be an option to open the SQL in the NB SQL editor. So, please don't get me wrong, in place editing would be awesome, but I think it would take a good amount of time to get the kinks worked out.

On the visual query tool, I had first marked it as unimportant, but then I thought about the times I have used a DB which wasn't so standard SQL friendly. In those cases the visual query tool would come in real handy I suppose, so I moved it to nice to have.

  • Trigger and Stored procedure development for some major databases like Oracle, DB2 and SQL Server.
  • Visualizing the database, letting the user selecting only a set of tables. Show relations.

Store the graphical layout between each time I want to see the same set of tables.

Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo