Oracle SQL Developer

More documents

Recommendations

Info

Designing TriggersNote: A procedure called by a trigger cannot run the previoustransaction control statements, because the procedure runs within thecontext of the trigger body.Statements inside a trigger can reference remote schema objects. However, pay specialattention when calling remote procedures from within a local trigger. If a timestamp orsignature mismatch is found during execution of the trigger, then the remoteprocedure is not run, and the trigger is invalidated.System Trigger RestrictionsOnly committed triggers are fired. For example, if you create a trigger that should befired after all CREATE events, then the trigger itself does not fire after the creation,because the correct information about this trigger was not committed at the time whenthe trigger on CREATE events was fired.For example, if you execute the following SQL statement:CREATE OR REPLACE TRIGGER my_triggerAFTER CREATE ON DATABASEBEGINNULL;END;Then, trigger my_trigger is not fired after the creation of my_trigger. OracleDatabase does not fire a trigger that is not committed.9.2.3 Privileges Needed to Work with TriggersTo create a trigger in your schema, you must have the CREATE TRIGGER systemprivilege, and either:■■Own the table specified in the triggering statement, orHave the ALTER privilege for the table in the triggering statement, or■ Have the ALTER ANY TABLE system privilegeTo create a trigger in another user's schema, or to reference a table in another schemafrom a trigger in your schema, you must have the CREATE ANY TRIGGER systemprivilege. With this privilege, the trigger can be created in any schema and can beassociated with any user's table. In addition, the user creating the trigger must alsohave EXECUTE privilege on the referenced procedures, functions, or packages.To create a trigger on DATABASE, you must have the ADMINISTER DATABASETRIGGER privilege. If this privilege is later revoked, then you can drop the trigger, butnot alter it.The object privileges to the schema objects referenced in the trigger body must begranted to the trigger owner explicitly (not through a role). The statements in thetrigger body operate under the privilege domain of the trigger owner, not the privilegedomain of the user issuing the triggering statement. This is similar to the privilegemodel for stored procedures.9-6 SQL Developer Online Help
10SQL*Plus: Usage InformationSQL*Plus is an interactive and batch command-line query tool that is installed withOracle Database. This topic includes the following topics:■■Overview of SQL*PlusUsing SQL*Plus10.1 Overview of SQL*Plus10.2 Using SQL*PlusSQL*Plus is a command-line tool for accessing Oracle Database. It enables you to enterand execute SQL, PL/SQL, and SQL*Plus commands to:■■■■Query, insert, and update dataExecute PL/SQL proceduresExamine table and object definitionsDevelop and run batch scripts■ Perform database administrationYou can use SQL*Plus to generate reports interactively, to generate reports as batchprocesses, and to output the results to text file, to screen, or to HTML file for browsingon the Internet.This topic describes SQL*Plus, Oracle's command line tool for executing SQL andPL/SQL.■■■■■See Also:■■SQL*Plus User's Guide and Reference for complete informationabout SQL*PlusOracle Database SQL Reference for information on using SQLstatementsStarting and Exiting SQL*PlusDisplaying Help With SQL*PlusEntering and Executing SQL Statements and CommandsSQL*Plus DESCRIBE CommandSQL*Plus SET CommandsSQL*Plus: Usage Information 10-1
Page 1 and 2:
Oracle SQL DeveloperOnline HelpRele
Page 3 and 4:
Contents1 SQL Developer Concepts an
Page 5 and 6:
3.12 Create/Edit Index ............
Page 7 and 8:
6.3.2 Updating Data With the UPDATE
Page 9:
10.2.5 SQL*Plus SET Commands.......
Page 12 and 13:
SQL Developer User InterfaceThe men
Page 14 and 15:
SQL Developer User InterfaceThe Com
Page 16 and 17:
Database Objects1.2 Database Object
Page 18 and 19:
Database Objectscontaining the mast
Page 20 and 21:
Database Objects■■■■■■
Page 22 and 23:
Database ConnectionsWhen you start
Page 24 and 25:
Running and Debugging Functions and
Page 26 and 27:
Using the SQL WorksheetRelated Topi
Page 28 and 29:
Using the SQL WorksheetScript Runne
Page 30 and 31:
Using the SQL Worksheetmentioned in
Page 32 and 33:
Reports1.9 ReportsRelated TopicsRun
Page 34 and 35:
Reports1.9.3 Table reportsTable rep
Page 36 and 37:
Reportsissues and vulnerabilities,
Page 38 and 39:
SQL Developer Preferencesand the SQ
Page 40 and 41:
SQL Developer Preferences1.10.3 Cod
Page 42 and 43:
SQL Developer PreferencesSQL Develo
Page 44 and 45:
SQL Developer User Information: Loc
Page 46 and 47:
Supplementary Oracle Database Infor
Page 48 and 49:
Creating a Table (Books)the table t
Page 50 and 51:
Creating a Table (Transactions)Colu
Page 52 and 53:
Creating a SequenceName: for_key_bo
Page 54 and 55:
Creating a PL/SQL Procedure2.6 Crea
Page 56 and 57:
Using the SQL Worksheet for Queries
Page 58 and 59:
Script for Creating and Using the L
Page 60 and 61:
Script for Creating and Using the L
Page 62 and 63:
Check for UpdatesTo remove the effe
Page 64 and 65:
Select Library3.8 Select LibraryThi
Page 66 and 67:
Create PL/SQL Function, Procedure,
Page 68 and 69:
Create Table (quick creation)Relate
Page 70 and 71:
Create/Edit Table (with advanced op
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Create Type (User-Defined)For more
Page 80 and 81:
Create/Edit ViewTest Syntax: Checks
Page 82 and 83:
Configure File Type AssociationsDia
Page 84 and 85:
Find/Replace TextTo add a type of o
Page 86 and 87:
Save/Save As3.37 Save/Save As3.38 S
Page 88 and 89:
SQL*Plus Location3-28 SQL Developer
Page 90 and 91:
Managing TablesTo include lowercase
Page 92 and 93:
Managing Tables4.2.4 Column Constra
Page 94 and 95:
Managing Indexes4.3 Managing Indexe
Page 96 and 97:
Managing Indexesuseful when all of
Page 98 and 99:
Managing Views4.4 Managing Views4.3
Page 100 and 101:
Managing Synonyms4-12 SQL Developer
Page 102 and 103:
Storing Numeric Data■■NCHAR and
Page 104 and 105:
Storing Numeric DataThe absence of
Page 106 and 107:
Storing Datetime Data5.4.1.2 Using
Page 108 and 109:
Storing Datetime Data5-8 SQL Develo
Page 110 and 111:
Retrieving Data With Queries■■
Page 112 and 113:
Retrieving Data With QueriesSee Als
Page 114 and 115:
Retrieving Data With QueriesSee Als
Page 116 and 117:
Transaction Control Statements6.3.2
Page 118 and 119: Using Pseudocolumns, Sequences, and
Page 124 and 125: Using SQL Data Definition Language
Page 126 and 127: Using SQL Data Definition Language
Page 128 and 129: Entering and Executing PL/SQL CodeY
Page 130 and 131: Utilizing the Main Features of PL/S
Page 148 and 149: Handling PL/SQL ErrorsTo handle une
Page 150 and 151: Handling PL/SQL ErrorsIf you redecl
Page 152 and 153: Handling PL/SQL Errors7-26 SQL Deve
Page 154 and 155: Overview of Packages and Subprogram
Page 156 and 157: Managing Packagescalling procedures
Page 158 and 159: Oracle Product-Specific PackagesTab
Page 160 and 161: Oracle Product-Specific PackagesTab
Page 162 and 163: Oracle Product-Specific Packages8-1
Page 164 and 165: Overview of Triggers9.1.1 Types of
Page 166 and 167: Overview of Triggers■■A trigger
Page 170 and 171: Using SQL*Plus■■■Running Scri
Page 172 and 173: Using SQL*PlusA SQL script file is
Page 174 and 175: Using SQL*Plus10-6 SQL Developer On
Page 176 and 177: Overview of Globalization Support
Page 178 and 179: Setting up the Globalization Suppor
Page 192 and 193: SQL and PL/SQL Programming with Uni
Page 194 and 195: SQL and PL/SQL Programming with Uni
Page 196 and 197: Locale-Dependent SQL Functions with
Page 198 and 199: Locale-Dependent SQL Functions with
Page 200 and 201: COLLECTION_IS_NULL exception, 7-22c
Page 202 and 203: overview, 7-14EXPLAIN PLANexecution
Page 204 and 205: NLSSORT SQL function, 11-21NO_DATA_
Page 206 and 207: displaying output from PL/SQL, 7-9s
Page 208: disabling, 9-4enabling, 9-4error co
show all

Oracle SQL Developer

Create successful ePaper yourself

Delete template?

Save as template?