SQL Assistant build 4.5 has been released

New features and enhancements

1. One-click comparison for code in the editor against code in database, files, other editors.
2. Optional display of table constraints and indexed columns in column popups and mouse-over hints.
3. Mouse-over hints for procedure and function parameters and for table and view columns.
4. Auto-connect feature for non-shared connections. Now you can associated db connections with your editor and forget about it, no need to use the Connect dialog repeatedly.
5. Support for DB2 aliases, sequences, and types.
6. Support for pass-through queries in MS Access.
7. Auto-completed INSERT and UPDATE statements now automatically check for and skip identity columns.
8. Support for SQL Scrapbook window in Eclipse and Eclipse based products.
9. Oracle procedural code compilation errors are now recognized and reported as code execution errors.
10. All popups now remember user-selected size.
11. All dialogs are now resizable.
12. Other minor enhancements and usability changes.

Bug fixes

1. SQL Assistant popups stop appearing after new db is created in SQL Server
2. Oracle ODBC-based connections may lead to "ORA-24374: define not done before fetch or execute and fetch"
3. Compatibility issues with PosgreSQL before 8.3 - automatic INET data type conversion to string is not handled by PosgreSQL before 8.3 release.
4. Certain types of errors captured during code execution in PostgreSQL may be reported twice.
5. Bracket highlighting is not updated after invocation of code formatting using the associated hot-keys.
6. Using "Show Table Data" in SQL*Plus always lead to Nothing is Selected error.
7. Using "Show Table Data" in "Toad for Oracle FREEWARE" always lead to Nothing is Selected error.
8. SQL Assistant dialogs are missing icons when SQL Assistant is used with recent Toad versions.

Last edited by SysOp on Tue Mar 10, 2009 12:53 am; edited 1 time in total

this tool is very good and it help us so much
but why such a good tool not support for chinese character?
for example i type select * from table where name like '%哈哈%'
there is an error

Please do not use version announcement topics for questions, Please create a new topic for every new question. It is much easier to reply and track. Supporting double-byte characters like Chinese is complicated. It is not just fonts that matter. All internal calculations, all internal buffers, text layout, etc… etc.. all of that depends on using multiple bytes for each character instead of single bytes. We are planning on implementing double-byte support in version 5.0