SQLGrinder 2 Release Notes

This blog documents the changes made in each version of SQLGrinder.

SQLGrinder 2 Beta 3 includes the following changes:

[ADDED] Added "All Columns" to search field menus, so that all columns of a result set can be searched at once.

[ADDED] User now prompted to save new logins upon successful connections to databases. Can be turned on and off in Login preferences.

[ADDED] Added an icon that shows the edit state of the data table in the schema browser. Only tables with primary keys can be edited.

[ADDED] SQL statements can now be sent with command-return as well as command-enter.

[ADDED] Added preference to automatically retrieve rows for data table when switching to the data tab in the schema browser. Thread for loading rows can also now be canceled.

[ADDED] Added schema qualifier to reduce schema retrieval data set. Primarily for Oracle users, the database in the login sheet can now be specified as SID:schema so that instead of the entire world being pulled back, which is what the Oracle JDBC driver returns, a specific schema and only that schema will be loaded. Usage: DevDB:SCOTT will retrieve only the SCOTT schema from the database with an SID of DevDB. This is a lot faster than pulling everything back and displaying it, even when you can't view and edit most of the schema outside of SCOTT and don't need that data.

[FIXED] Resolved issues related to switching to working offline while editing schema browser data table.

[FIXED] Hitting return to end schema browser data table change now updates data correctly.

[FIXED] Keyword completion now works when keyword is proceeded by a period character.

[FIXED] Fixed "File Has Been Modified" message that was being displayed when it shouldn't have been.

[FIXED] Resolved problems with new syntax color defaults not getting initialized correctly. This also fixes a potential crash condition when logging in.

[FIXED] Resolved a problem where "Show Library" and "Message Log" toolbar buttons never enabled.

[FIXED] Resolved issue where picking database from combo menu wasn't marking the login as changed, so the value wasn't used.

There are still some known issues with Oracle, including lack of procedure package support when displaying procedures.