Tchater maintenant avec le support
Tchattez avec un ingénieur du support

SQL Navigator for Oracle 7.4 - User Guide

Quick Overview Working With SQL Navigator Navigation Oracle Logon Code Editor Visual Object Editors Team Coding and Version Control Systems Modules, Windows And Dialogs
Analyze Tool Auto Describe Tool Benchmark Factory Bookmarks Dialog Capture Web Output Change Logon Password Dialog Code Analysis Code Assistant Code Road Map Code Templates Code Test Database Source Code Search Dialog DB Navigator Describe Difference Viewer Edit Data ER Diagram Explain Plan Tool Export Table Find and Replace Dialog Find objects Dialog Find Recycle Bin Objects Dialog Formatting Options HTML Viewer Import HTML as PL/SQL Import Table Java Manager Job Scheduler Locate In Tree Output Window PL/SQL Profiler Profile Manager Project Manager Publish Java to PL/SQL Quick Browse Rename Object Search Knowledge Xpert Select DB Object Dialog Server Output Server Side Installation Wizard Session Browser Source Preview SQL Modeler SQL Optimizer Task Manager Web Support Configuration Dialog Wrap Code
View | Preferences About Us

Bookmarks Dialog

Modules, Windows And Dialogs > Bookmarks Dialog

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.

Capture Web Output

Modules, Windows And Dialogs > Capture Web Output

When you first log in to SQL Navigator, the Web server is not enabled for use.

 

Start Capturing Web Output

  1. Click Session | Capture Web Output.
  2. Verify that the Oracle Web Toolkit is installed and visible to the schema. Check the Output Window for a confirmation message.

 

While Capturing Web Output

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.

Change Logon Password Dialog

Modules, Windows And Dialogs > Change Logon Password Dialog

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

Modules, Windows And Dialogs > Code Analysis

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.

 

Access to Code Analysis

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.

 

Rules and Rule Sets

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 Metrics

Code Analysis uses a variety of metrics to evaluate code, including the following:

  • Computational Complexity (Halstead Volume)—Measures a program module's complexity directly from source code, with emphasis on computational complexity. The measures were developed by the late Maurice Halstead as a means of determining a quantitative measure of complexity directly from the operators and operands in the module. Among the earliest software metrics, they are strong indicators of code complexity. Because they are applied to code, they are most often used as a maintenance metric.
  • Cyclomatic Complexity (McCabe's)—Cyclomatic complexity is the most widely used member of a class of static software metrics. It measures the number of linearly-independent paths through a program module. This measure provides a single ordinal number that can be compared to the complexity of other programs. It is independent of language and language format.

  • 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.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation