Keyword and parameter description - delete statement, PL-SQL Programming

Assignment Help:

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. 


Related Discussions:- Keyword and parameter description - delete statement

Keyword & parameter description - exceptions, Keyword & Parameter Descripti...

Keyword & Parameter Description: WHEN: This keyword introduces the exception handler. You can have many exceptions execute the similar sequence of the statements by follo

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 the pls_integer datatype - performance of application, Use the PLS_INTE...

Use the PLS_INTEGER Datatype When you require to declare an integer variable, use the datatype PLS_INTEGER that is the most efficient numeric type. That is as the PLS_INTEGER

%found - explicit cursor attributes, %FOUND Subsequent to a cursor or ...

%FOUND Subsequent to a cursor or cursor variable is opened but before the first fetch, the %FOUND yields NULL. Afterward, it yields TRUE when the last fetch returned a row, or

Interesting properties of cross join - sql, Interesting properties of CROSS...

Interesting properties of CROSS JOIN - SQL Compare these with the "interesting properties of JOIN", CROSS JOIN is associative but not commutative. Unlike JOIN and NATURAL JOI

Processing transactions, Processing Transactions This part describes ho...

Processing Transactions This part describes how to do the transaction processing. You learn the fundamental techniques that safeguard the consistency of your database, involvin

Case sensitivity-naming conventions, Case Sensitivity Similar to all the...

Case Sensitivity Similar to all the identifiers, the variables, the names of constants, and parameters are not case sensitive. For illustration, PL/SQL considers the following n

Committing and rolling back - autonomous transaction, Committing and Rollin...

Committing and Rolling Back The COMMIT and ROLLBACK end the active autonomous transaction but do not exit the autonomous routine. As the figure shows, if one transaction ends,

Cursor for loops, Cursor FOR Loops In most cases that need an explicit ...

Cursor FOR Loops In most cases that need an explicit cursor, you can simplify the coding by using a cursor FOR loop rather of the OPEN, FETCH, and CLOSE statements. A cursor FO

Using aliases-declarations in sql, Using Aliases The Select-list items f...

Using Aliases The Select-list items fetched from a cursor related with the %ROWTYPE should have simple names or, if they are expressions, should have aliases. In the example bel

Write Your Message!

Captcha
Free Assignment Quote

Assured A++ Grade

Get guaranteed satisfaction & time on delivery in every assignment order you paid with us! We ensure premium quality solution document along with free turntin report!

All rights reserved! Copyrights ©2019-2020 ExpertsMind IT Educational Pvt Ltd