View / Go to / Delete bookmarked lines in the code.
Option | Description |
---|---|
List of bookmarks | Click on a bookmark to highlight it. |
Jump | View the highlighted bookmark in an editor. |
Delete | Delete the highlighted bookmark. |
|
TIP: More bookmark actions can be found on the Edit Menu. |
When you first log in to SQL Navigator, the Web server is not enabled for use.
Each time you execute PL/SQL code that generates HTML output, the generated HTML is displayed in the HTML Viewer.
|
Note: If the PL/SQL procedure is run under the debugger, the HTML output is not visible until the procedure is complete. |
Modify the logon password of the current session.
Option | Description |
---|---|
Old password | The password you used to logon to the Oracle session. |
New password | What you want to change the password to. |
Verification | Type the new password twice: once in the New password box and then again in the Verification box. |
Code Analysis is an automated code review and analysis tool. It enables individual developers, team leads, and managers to ensure that the quality, performance, maintainability, and reliability of their code meets and exceeds their best practice standards.
|
Note: This feature is available in the Professional Edition and higher. |
Code Editor | Code Analysis is available in the Code Editor, which ensures code quality from the beginning of the development cycle. In the Code Editor, Code Analysis evaluates how well a developer's code adheres to project coding standards and best practices by automatically highlighting errors and suggesting smarter ways to build and test the code. |
Code Analysis Window | SQL Navigator also provides a dedicated Code Analysis window, where you can perform more detailed analysis, evaluate multiple scripts at the same time, and view a detailed report of the analysis. |
Code Analysis compares code against a set of rules (Code Analysis Rules) for best practices. These rules are stored in rule sets (Code Analysis Rule Sets).
The Code Analysis rules and rule sets can be adjusted to suit the requirements of different projects. Regardless of whether developers are responsible for their own code quality or if this needs to be managed centrally, Code Analysis can be adapted to fit either need.
Code Analysis uses a variety of metrics to evaluate code, including the following:
Maintainability Index (MI)—Quantitative measurement of an operational system's maintainability is desirable both as an instantaneous measure and as a predictor of maintainability over time. This measurement helps reduce or reverse a system's tendency toward "code entropy" or degraded integrity, and to indicate when it becomes cheaper and/or less risky to rewrite the code than to change it. Applying the MI measurement during software development can help reduce lifecycle costs.
The Code Analysis Report includes detailed descriptions of the code metrics and how they work. For more information, see Code Analysis Window.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 이용 약관 개인정보 보호정책 Cookie Preference Center