A new preference has been added to simplify the process of opening a new SQL file in an editor other than the SQL Text Editor. If you look at Data Management->SQL Development->SQL Editor->SQL Files/Scrapbook, you'll see a new checkbox on the page labeled "SQL file is default opened after creation". If checked (default behavior), any new SQL file will open in the SQL Text Editor as in the past. If unchecked, the file will not be opened and can then be opened in a text editor or the graphical SQL Query Editor.

Previously when you'd have a SQL file in the SQL Text Editor and used "refresh from server" in the context menu, the cursor would jump to the top of the editor. Now it tries to save the position and restore it after the refresh.

Back in our Ganymede release, we did a lot of refactoring work to separate framework and other plug-ins into UI and non-UI chunks for better encapsulation. In Galileo, the SQL Dev Tools team has done a great amount of work to refactor the SQL Dev Editor framework into UI and non-UI chunks.

For Galileo, we have a new extensible SQL Schema Editor Framework and an exemplary implementation for the Sybase ASA enablement project. The schema editor includes schema editors for tables, indices, triggers, views, stored procedures, user-defined types, user-defined functions, and events.

In the case where a SQL statement is run and takes a long time to complete, there has traditionally been no way to cancel it. The user can now cancel a long-running SQL action and be returned to the UI.

Sometimes if you have huge result sets, it takes a long time to re-load them when you restart and can sometimes cause resource-related issues. This fix also includes a new preference that allows you to clear the result history when the Eclipse workbench is shut down.