Oracle SQL Developer

More documents

Recommendations

Info

Utilizing the Main Features of PL/SQLExample 7–28 illustrates several uses of dynamic SQL.Example 7–28Examples of Dynamic SQL-- create a standalone procedureCREATE OR REPLACE PROCEDURE raise_emp_salary (column_value NUMBER,emp_column VARCHAR2, amount NUMBER) IScolumn VARCHAR2(30);sql_stmt VARCHAR2(200);BEGIN-- determine if a valid column name has been given as inputSELECT COLUMN_NAME INTO column FROM USER_TAB_COLSWHERE TABLE_NAME = 'EMPLOYEES' AND COLUMN_NAME = emp_column;sql_stmt := 'UPDATE employees SET salary = salary + :1 WHERE '|| column || ' = :2';EXECUTE IMMEDIATE sql_stmt USING amount, column_value;IF SQL%ROWCOUNT > 0 THENDBMS_OUTPUT.PUT_LINE('Salaries have been updated for: ' || emp_column|| ' = ' || column_value);END IF;EXCEPTIONWHEN NO_DATA_FOUND THENDBMS_OUTPUT.PUT_LINE ('Invalid Column: ' || emp_column);END raise_emp_salary;/DECLAREplsql_block VARCHAR2(500);BEGIN-- note the semi-colons (;) inside the quotes '...'plsql_block := 'BEGIN raise_emp_salary(:cvalue, :cname, :amt); END;';EXECUTE IMMEDIATE plsql_block USING 110, 'DEPARTMENT_ID', 10;EXECUTE IMMEDIATE 'BEGIN raise_emp_salary(:cvalue, :cname, :amt); END;'USING 112, 'EMPLOYEE_ID', 10;END;/DECLAREsql_stmtVARCHAR2(200);columnVARCHAR2(30) := 'DEPARTMENT_ID';dept_id NUMBER(4) := 46;dept_nameVARCHAR2(30) := 'Special Projects';mgr_id NUMBER(6) := 200;loc_id NUMBER(4) := 1700;BEGIN-- note that there is no semi-colon (;) inside the quotes '...'EXECUTE IMMEDIATE 'CREATE TABLE bonus (id NUMBER, amt NUMBER)';sql_stmt := 'INSERT INTO departments VALUES (:1, :2, :3, :4)';EXECUTE IMMEDIATE sql_stmt USING dept_id, dept_name, mgr_id, loc_id;EXECUTE IMMEDIATE 'DELETE FROM departments WHERE ' || column || ' = :num'USING dept_id;EXECUTE IMMEDIATE 'ALTER SESSION SET SQL_TRACE TRUE';EXECUTE IMMEDIATE 'DROP TABLE bonus';END;/-- rollback the changesROLLBACK;-- delete the procedureDROP PROCEDURE raise_emp_salary;7-20 SQL Developer Online Help
Handling PL/SQL Errors7.3.16 Using Bind VariablesWhen you embed an INSERT, UPDATE, DELETE, or SELECT SQL statement directly inyour PL/SQL code, PL/SQL turns the variables in the WHERE and VALUES clauses intobind variables automatically. Oracle can reuse these SQL statement each time the samecode is executed. To run similar statements with different variable values, you can saveparsing overhead by calling a stored procedure that accepts parameters, then issuesthe statements with the parameters substituted in the appropriate places.You do need to specify bind variables with dynamic SQL, in clauses like WHERE andVALUES where you normally use variables. Instead of concatenating literals andvariable values into a single string, replace the variables with the names of bindvariables (prefixed by a colon) and specify the corresponding PL/SQL variables withthe USING clause. Using the USING clause, instead of concatenating the variables intothe string, reduces parsing overhead and lets Oracle reuse the SQL statements.In Example 7–28, :1 and :2 are bind variables for amount and column_value. In thesame example, there are additional bind variables, such as :cvalue, :cname, and:amt.7.4 Handling PL/SQL ErrorsPL/SQL makes it easy to detect and process error conditions known as exceptions.When an error occurs, an exception is raised: normal execution stops and controltransfers to special exception-handling code, which comes at the end of any PL/SQLblock. Each different exception is processed by a particular exception handler.PL/SQL exception handling is different from the manual checking you might be usedto from C programming, where you insert a check to make sure that every operationsucceeded. Instead, the checks and calls to error routines are performed automatically,similar to the exception mechanism in Java programming.Predefined exceptions are raised automatically for certain common error conditionsinvolving variables or database operations. For example, if you try to divide a numberby zero, PL/SQL raises the predefined exception ZERO_DIVIDE automatically. See"Summary of Predefined PL/SQL Exceptions" on page 7-21.You can declare exceptions of your own, for conditions that you decide are errors, or tocorrespond to database errors that normally result in ORA- error messages. When youdetect a user-defined error condition, you execute a RAISE statement. See "DeclaringPL/SQL Exceptions" on page 7-23.This topic includes the following topics:■ Summary of Predefined PL/SQL Exceptions■ Using the Exception Handler■ Declaring PL/SQL Exceptions■ Scope Rules for PL/SQL Exceptions■ Continuing After an Exception is Raised7.4.1 Summary of Predefined PL/SQL ExceptionsAn internal exception is raised automatically if your PL/SQL program violates anOracle rule or exceeds a system-dependent limit. PL/SQL predefines some commonOracle errors as exceptions. For example, PL/SQL raises the predefined exception NO_DATA_FOUND if a SELECT INTO statement returns no rows.PL/SQL: Usage Information 7-21
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 168 and 169: Designing TriggersNote: A procedure
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?