Keyword and Parameter Description:

table_reference:

This specifies a table or view that should be accessible when you execute the DELETE statement, and for that you must have DELETE privileges.

Subquery:

This is a SELECT statement which provides a set of rows for the processing. Its syntax is such that of select_into_statement without the INTO clause.

TABLE (subquery2):

The operand of the TABLE is a SELECT statement which returns a single column value, that should be a nested table or a varray cast as a nested table. The Operator TABLE informs the Oracle that the value is a collection, but not a scalar value.

Alias:

This is another (generally short) name for the referenced table or view and is usually used in the WHERE clause.

WHERE search_condition:

This clause provisionally chooses the rows to be deleted from the referenced table or the view. Only rows which meet the search condition are deleted. If you omit the WHERE clause, then all rows in the table or view are deleted.

WHERE CURRENT OF cursor_name:

This clause refers to the most recent row processed by the FETCH statement related with the cursor identified by the cursor_name. The cursor should be FOR UPDATE and should be open and placed on a row. When the cursor is not open, the CURRENT OF clause causes an error.

When the cursor is open, but no rows have been fetched or the last fetch returned no rows, then PL/SQL raises the predefined exception NO_DATA_FOUND.

returning_clause:

This clause returns values from the deleted rows, by this means eliminating the need to SELECT the rows ahead of time. You can retrieve the column values into the variables and/or host variables, or into the collections and/or host arrays. Though, you cannot use the RETURNING clause for remote or parallel deletes.

BULK COLLECT:

These clauses instruct the SQL engine to bulk-bind the output collections before returning them to the PL/SQL engine. The SQL engine bulk-binds all the collections referenced in the RETURNING INTO list. The corresponding columns should store scalar (and not the composite) values. 

Posted Date: 10/8/2012 6:01:57 AM | Location : United States

Ask an Expert

Related Discussions:- Keyword and parameter description - delete statement, Assignment Help, Ask Question on Keyword and parameter description - delete statement, Get Answer, Expert's Help, Keyword and parameter description - delete statement Discussions

Write discussion on Keyword and parameter description - delete statement
Your posts are moderated

Write your message here..

Related Questions

Entering and exiting - autonomous transaction, Entering and Exiting If... Entering and Exiting If you enter the executable part of an autonomous routine, the major transaction suspends. When you exit the routine, the major transaction resumes. To ex

Use of table comparisons - sql, Use of Table Comparisons - SQL Table ... Use of Table Comparisons - SQL Table comparisons where it is noted that although table expressions cannot be compared, we have TABLE (t) to convert a table expression t into

%type attribute - syntax, %TYPE Attribute The %TYPE attribute gives the... %TYPE Attribute The %TYPE attribute gives the datatype of a record, field, nested table, database column, or the variable. You can use the %TYPE attribute as the datatype speci

Library system, Hi,am developing a library system and relating all the tabl... Hi,am developing a library system and relating all the table is somehow complex,could you kindly assist me

Iteration schemes- iterative control, Iteration Schemes The bounds of a ... Iteration Schemes The bounds of a loop range can be variables, literals, variables, or expressions but must compute to integers. Below are some of the examples. As you can see t

Need for dynamic sql - pl sql , Need for Dynamic SQL: You need dynamic... Need for Dynamic SQL: You need dynamic SQL in the situations as follows: 1) You would like to execute a SQL data definition statement (like CREATE), a data control statemen

Using rollback - , Using ROLLBACK The ROLLBACK statements end the pres... Using ROLLBACK The ROLLBACK statements end the present transaction and undo any change made during the transaction. The Rolling back is helpful for two reasons. Firstly, if yo

Fetching with a cursor, Fetching with a Cursor The FETCH statements re... Fetching with a Cursor The FETCH statements retrieve the rows in the result set one at a time. After each and every fetch, the cursor advance to the next row in the result set

Parameter and keyword description - update statement, Parameter and Keyword... Parameter and Keyword Description:   table_reference: This keyword identifies the table or view that should be accessible when you execute the UPDATE statement, and for wh

Using %rowtype-declarations in sql, Using %ROWTYPE The %ROWTYPE attribut... Using %ROWTYPE The %ROWTYPE attribute gives a record type which represents a row in a table (or view). The record can store the whole row of data selected from the table or fetc