These release notes provide information about the SQL Navigator® release.
Thank you for installing SQL Navigator, the Professional Oracle Development Environment of choice for thousands of developers and corporations worldwide.
SQL Navigator provides an integrated environment for developing and testing stored programs, schemas, SQL scripts, and more - all from an easy-to-use graphical user interface. The SQL Navigator family of products is a complete development environment for Oracle server-side development and management. It has been conceived, designed and developed by Oracle developers and DBAs with hands-on experience in the most common problems facing Oracle developers.
View the latest Release Notes containing late-breaking information and known issues about SQL Navigator.
We trust you will find that SQL Navigator significantly improves your productivity, so that your projects are completed faster with a higher level of quality than ever before.
SQL Navigator 8.0 is a major release, with enhanced features and functionality.
Table 1: General enhancements
|SQL Navigator now supports Microsoft Server 2022 and Oracle 21c.
|SQL Navigator now supports noneditable keywords for Triggers/ Functions/Packages/Package Body.
|We have upgraded to the latest edition of QP5 in order to access the most recent formatting and parsing syntax capabilities.
|All the third party tools have been upgraded to their most latest versions.
|SQL Navigator now supports Windows 11.
Table 2: General resolved issues
|Users are experiencing slowness when when loading large size PL/SQL packages. This issue has been observed following an upgrade from SQL Navigator version 5.5 to 7.6.
|The Zlib library has been upgraded from 1.2.7 to 1.2.13 in order to address issues related to the WhiteSource scan.
|SQL Navigator is encountering slow loading times across various screens and functions, particularly when interacting with triggers.
|Users are unable to extract a Data Definition Language (DDL) using the 'Use EDITIONABLE OR NONEDITIONABLE' parameter through SQL Navigator.
|SQL Navigator encounters slow loading times when attempting to open large objects containing more than 10,000 lines from a database. This issue has been observed across versions 7.6, 7.4, and 7.1.
|SQL Navigator displays the 'ORA-9000: invalid SQL Statement' error when a user tries to execute a query for creating a noneditable procedure.
|Users are unable to compile extracted metadata using the Get Metadata function when the 'EDITIONABLE' clause is present in the Data Definition Language (DDL) definition.
|SQL Navigator displays an error when users attempt to format code containing case statements in versions 7.5 and 7.4.
|The update checker in SQL Navigator 7.4 displays inaccurate information when accessed through the Help > Check for Updates section.
Table 3: Known Issues
|Objects or tables updated in the database are not reflecting in the VCS repository, even after creating a new revision.
|The Result section on the 'SQL Navigator Server Side Installation' window is not displaying the status of the server-side installation when the installation fails.
The following options are not enabled in SQL Navigator under the Team Coding menu:
|The Explain Plan is not displaying the required parameters when opened using the Explain Plan icon in the icon tray.
|SQL Navigator is not displaying source code previews for any object in the Source Preview window.
|SQL Navigator generates a query with an incorrect format for the 'Getmeta data' script in the Editor tab.
|The Output window on the Profile Code page displays an incorrect count under the Code Statistics Summary section.
|When a user attempts to activate the 'Developer Edition' license, SQL Navigator displays incorrect licensed version information in the 'About SQL Navigator' window.
|SQL Navigator displays incorrect license information on the "About SQL Navigator" window when a user tries activating the "Developer Edition" license.
|Error message received while executing a stored procedure when the table is not present in the database, is not clear.
Pre-open F1 help is unresponsive when there is a modal dialog opened in SQL Navigator.
Workaround: Close the modal dialog and then switch to the help window
Export Data containing special characters from data grid to xlsx format may corrupt the Excel file. This usually happens when binary content is exported from a BLOB field.
Workaround: Exclude the rows or columns which contain binary data or special characters when using the Export Data dialog
Table 4: Third Party Known Issues
|When users connect to the Oracle 19c database for the first time after upgrading from an Oracle 12c database, SQL Navigator displays an error. This issue is particularly observed with tables containing XMLTYPE columns.
|E-Control (Editor component)
|Odd word-wrapping behavior in some languages. Word wrapping may appear between symbols, with no space required to wrap, and some characters cannot be word-wrapped at all (for example, multi-byte characters in ANSI text).
|ODAC does not support Unicode in XMLTYPE (editing of XMLTYPE data is not supported). Querying of XMLTYPE with binary storage will lead to an error.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback 이용 약관 개인정보 보호정책 Cookie Preference Center