Columns
The Columns window provides an easy-to-use tool to arrange and hide/show columns of the retrieved table in the data grid.
|
|
TIP: Run a valid query statement to populate the window. |
| Action | Description |
|---|---|
| Show/Hide columns | Show selected columns. Hide deselected columns. |
| Select column | Click on the column's name. |
| Arrange columns | Click Move Up or Move Down. |
|
|
Note: The settings will be saved and taken into account when you refresh or rollback the query. However if you rerun the query, the settings will be set back to default. |
Visual Object Editors
SQL Navigator’s editing tools for database objects:
- Are visual. They give you a graphical representation of a database object definition. This makes it easy to see relationships and properties.
- Allow you to view database object definitions and create or alter database objects via a point-and-click interface, eliminating the need to remember SQL syntax and write SQL statements manually.
- Generate the DDL or other database code automatically when you create or alter a database object. You can also and edit the code directly, if needed.
When opened, a visual object editor connects to the active database session (Session Menu | Select).
| Object | Object Type | SQL Navigator Visual Object Editor | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
Schema |
Indexes |
||||||||||
| Database Links | Database Link Editor | ||||||||||
| Materialized (Snapshot) Views | Materialized View Editor | ||||||||||
| Sequences | Sequence Editor | ||||||||||
|
Synonyms |
| ||||||||||
| Varying arrays | Varray Editor | ||||||||||
| Triggers | Now in the Code Editor. | ||||||||||
| Views | View Editor | ||||||||||
|
Non-Schema |
Users |
||||||||||
| Roles | Role Editor | ||||||||||
| Profiles | Profile Editor | ||||||||||
| Instance properties | Instance Property Editor | ||||||||||
| Redo Log Groups | Redo Log Group Editor |
Cluster Editor
Use the cluster editor to join tables that are closely related for storing on the same area of the disk. This lets you interleave the rows of two or more tables together into a single area called a cluster.
|
About Cluster Objects |
The cluster key is the column or columns by which the tables are usually joined in a query. You can only cluster together tables that you own. You can create either an index cluster or a hash cluster. With an indexed table or index cluster, Oracle locates the rows in a table using key values that Oracle stores in a separate index. To use hashing, you create a hash cluster and load tables into it. Oracle physically stores the rows of a table in a hash cluster and retrieves them according to the results of a hash function. The characteristics and usage of this database object are described in the Oracle documentation. |
Ways to Open The Cluster Editor
| Icon | Action | Description |
|---|---|---|
| |
From the Main Menu View Menu | Visual Object Editors | Cluster Editor |
Open the Cluster Editor. |
| |
From DB Navigator or Find objects Dialog Right click on a Cluster object and click Open. |
Open the selected Cluster object in the Cluster Editor. |
Constraint Editor
Use the Constraint Editor to specify table constraints.
|
About Constraints |
In Oracle, a constraint is a rule applied to an object that restricts the data allowed in any instance of the object. The characteristics and usage of this database object are described in the Oracle documentation. |
|
|
Note:
|
Using The Editor
Steps To Create A Constraint
-
Click Create a new constraint to open the New Constraint dialog.
Field Description Parent Schema Select the parent schema for the new constraint. Parent Object Select the parent object (table) for the new constraint. Name Name the new constraint. Constraint Type
Type Purpose Check Specifies a condition that each row in the table must satisfy Primary Key Designates a column or combination of columns as a table’s primary key Unique Designates a column or combination of columns as a table’s unique key Foreign Key Designates a column or combination of columns as the foreign key -
More on the Constraint Type.
Type
Action
Check
Enter the check condition following Oracle syntax conventions. Example: (loc is not null)
Primary Key
Designate the column(s) to be used as the Unique, Primary Key, or Foreign key.
To add columns to the constraint, use the arrow button to move one or more selected columns from the Available Table Columns pane to the Constraint Columns pane. The double arrow adds all available columns to the constraint.
Unique
Foreign Key
- If the constraint type is Foreign key:
- Designate the Unique or Primary Key in the Reference field.
- If desired, select the On Delete Cascade property.
Note: Before selecting the On Delete Cascade property, be sure you understand the potential consequences of using this option. It could result in lost data. Consult your Oracle documentation for information about the DELETE CASCADE command.
Now the constraint is defined
| Icon | Tool Tip | Description |
|---|---|---|
 |
Generate SQL for changes |
Extract the DDL for the new constraint and place it into the Code Editor. |
 |
Revert to previous constraint |
Undo your entries without saving them. After saving your changes, you will not be able to use the Revert command. |
 |
Apply changes to DB |
Save your new constraint definition to the database. SQL Navigator generates the DDL and commits it to the database. |
 |
Enable current constraint |
This duplicates Enable/Disable Constraint on the Object Menu. |
Ways to Open The Constraint Editor
| Icon | Action | Description |
|---|---|---|
| |
From the Main Menu View Menu | Visual Object Editors | Constraint Editor |
Open the Constraint Editor. |
| |
From DB Navigator or Find objects Dialog Right click on a Constraint object and click Open. |
Open the selected Constraint object in the Constraint Editor. |