What's new in SQL Navigator 8.1.1?
Enhancements:
| Enhancement | Issue ID |
|---|---|
|
SQL Navigator now provides tolerance support of Oracle AI Database 26ai (formerly known as 23ai). https://blogs.oracle.com/database/post/oracle-announces-oracle-ai-database-26ai | SQLNAV-2491 |
| SQL Navigator now supports the latest patches of Windows 11, Windows Server 2022, and Windows Server 2025. | SQLNAV-2492 |
| SQL Navigator now provides enhanced Team Coding support for Azure DevOps Services (TFVC), Microsoft Azure DevOps Server - formerly known as Team Foundation Server (TFS) - covering versions 2019, 2020, and 2022. | SQLNAV-2493 |
Resolved Issues:
| Resolved Issue | Issue ID |
|---|---|
| Users experience refresh issues in Team Coding when multiple database users attempt to simultaneously check out and check in the same package. | SQLNAV-2519 |
| When comparing contents in the Team Coding Manager Revision History using SQL Navigator on Azure DevOps 2022, SQL Navigator displays the Error loading C:\users\DEWOLFFM\Appdata\local\temp\Nav7OESG error. | SQLNAV-2487 |
| SQL Navigator is generating incorrect DDL statements for identity columns for primary key. | SQLNAV-2485 |
| Code Assist (IntelliSense) does not fully support all DML statements. Issues occur particularly with nested DML statement aliases, especially in UPDATE queries, subqueries, and when using grouping functions such as SUM, MAX, and others. | SQLNAV-2483 |
| Users are unable to export query result table data to the latest Excel file format (.xlsx). | SQLNAV-2480 |
| TFS Team Coding restricts users from entering more than 255 characters in the comment box during object check-in and check-out. When the character limit is exceeded, SQL Navigator displays the warning message: Maximum 255 characters allowed. | SQLNAV-2478 |
| When users select specific schema options (rather than Select All) while checking in objects through TFS, SQL Navigator checks in all items regardless of the selections made in the dialog. | SQLNAV-2475 |
| Users are unable to manually remove the time component from a date field in the editor. The time value can only be cleared through the GUI menu, not by typing directly into the field. | SQLNAV-2468 |
| When users check out the package specification from SVN, both the package specification and body are locked, whereas only the specification is expected to be locked. The same behavior occurs during check-in when unlocking the package specification. | SQLNAV-2467 |
| In tables with multiple triggers, after editing and saving one trigger, opening another from the DB Navigator may display the previously edited trigger instead of the selected one. | SQLNAV-2466 |
| When users execute a SELECT query with an ORDER BY ASC clause on a date column and then switch to another tab, SQL Navigator does not retain the ORDER BY statement. | SQLNAV-2465 |
| Users are unable to update records through the grid interface (F2) when working with Oracle tables that use double quotes in field names. If the query involves tables with double-quoted fields, record updates via the grid result UI do not function as expected. | SQLNAV-2456 |
| After using the Find and Replace option, users are unable to manually replace text in the editor. | SQLNAV-2454 |
| Objects or tables updated in the database are not reflecting in the VCS repository, even after creating a new revision. | SQLNAV-2450 |
|
The following options are not enabled in SQL Navigator under the Team Coding menu:
| SQLNAV-2448 |
| SQL Navigator generates a query with an incorrect format for the Get Metadata script in the Editor tab. | SQLNAV-2443 |
| When using SQL Navigator to generate stubs while executing a function from a package, the output generated from Oracle 12c differs from that generated from Oracle 19c. | SQLNAV-2314 |
Further details can be found in the Release Notes here
