13-May-2003 -- news_V348

Piper: Version 3.48 New Features and Maintenance Release

• Toolbar buttons for Commit and Rollback at last! The new toolbar images are a Heart (for Commit.. you love it) and a Club (for Rollback.. you want to hit it on the head). These buttons (and their corresponding new SQL-menu items) will be automatically enabled when a transaction has been started. Currently, for long rollback operations, no feedback at the start of the operation is supplied in the log window.
• If you close a document or exit Piper or disconnect, while an Oracle transaction is open, you will be prompted to either commit or rollback first. Previous versions of Piper automatically committed work at close or disconnect time.
• The SQL History list now accumulates additional statistics for saved statements, and shows those statistics as extra columns alongside the saved statement: Length of statement in bytes, Execution time in milliseconds, Number of rows returned, and timestamp at last execution. These statistics are saved with the document.
• Entries in the SQL History list can now be sorted by any of its fields by clicking on the column header. An additional click will reverse-sort the entries. Entries for which no statistics have yet been accumulated, will sort in their original load order. To revert the whole list to the original load order, a new toolbar button and menu option in the Session Group are available.
• A crash was occuring, soon after connection, when the server-generated version identification string was unusually long. Fixed.
• In the Catalog Browser, the Edit button was generating incorrect syntax for Public Synonyms. Fixed.
• The keyboard commands Ctrl-[ and Ctrl-], which move to the previous and next entries in the SQL History list regardless of window focus, had been disabled in a previous maintenance release. Now available again.
• Various minor low-level bug fixes in this release. If something was not right, try it again. If it's still not right, please tell us about it.
• Piper is now built as a Microsoft Installer (.msi) file. However, it still can be deployed as a stand-alone .exe .