First, the new Explorer in ObjectDB is fantastic! This is exactly what we've needed - an easy way to do ad-hoc JPQL queries and navigate through the results and even make small changes to primitive data and Strings.
After playing with it for a while, here is a list of additional features I'd love to have:
1. Export of selected data:
a. Simple - Select a range of cells or a column header and copy text to the clipboard or save to a file (csv, html, etc..). (There appear to be copy menu options, but I cannot get them to work.)
b. XML - Select some objects and serialize them to XML (using ids for circular references)
c. Binary - Select some objects, serialize the data to a binary file. Then allow import of that file into another database.
2. Lazy loading of data, especially in table view - With large amounts of data, it takes a long time for the Swing Table or Tree views to display. Any movement of the scrollbar also causes large pauses (> 30 seconds in some cases). I am using remote servers, it may be faster for local files.
3. On the Query page, please add a checkbox to request the Results either as a table or tree.
4. It would be terrific if the Database tab had lots more information about the database health
a. Show actual running values for all parameters in objectdb.conf (size, threads, query-cache, memory usage, etc...) to use for tuning
b. Show all database connections, allow to close individual or all.
c. Buttons to restart database, hot backup (remote server to local HD), etc...
5. Evaluation of expressions when editing fields - It would be very useful to be able to enter a Java expression into a field. For example, suppose you have a User entity with a password field. I would like to enter SHA1.hash("mypassword"); You might use beanshell for the expression evaluation.
For me, #1, #2 and #3 would be the most important.
Also, I've found some small bugs:
1. Auto-login of last opened (remote) database puts the full URL into the Database Path field, when it should be only the database path. This causes an error on starting Explorer.exe. Same when opening 'recent connections'.
2. When editing a field in an @Embedded object, I get an error message: "Attempt to lock a non entity object". The change stays on the screen, but is not persisted to the database.
Again, many thanks for a tremendously useful new addition to ObjectDB.