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

Defining autonomous transactions, Defining Autonomous Transactions To ...

Defining Autonomous Transactions To define an autonomous transaction, you use the pragma (compiler directive) AUTONOMOUS_TRANSACTION. The pragma instructs the PL/SQL compiler

Parameter aliasing, Parameter Aliasing   To optimize the subprogram ca...

Parameter Aliasing   To optimize the subprogram call, the PL/SQL compiler can decide between the two techniques of the parameter passing. With the by-value techniques, the v

Mechanistis theory-haeckel - origin of life, MECHANISTI S THEORY-HAECKEL (...

MECHANISTI S THEORY-HAECKEL (1866) - Haeckel stating that after each catalysm, some new organism suddenly forms as a chance event in one stride from inanimate matter and sub

Indeterminacy in sql, Indeterminacy in SQL Some SQL expressions are ac...

Indeterminacy in SQL Some SQL expressions are actually not function invocations at all in the mathematical sense, being indeterminate-invocations operating on identical input

Keys in sql, Keys in SQL SQL support for keys in the following respect...

Keys in SQL SQL support for keys in the following respects: SQL does not require at least one key for every base table. If no key is explicitly declared, then KEY {ALL B

Transaction visibility, Transaction Visibility As the figure shows, th...

Transaction Visibility As the figure shows, the changes made by an autonomous transaction become visible to another transaction whenever the autonomous transaction commits. Th

Data types and representations, Data Types and Representations This ex...

Data Types and Representations This explains the concept possible representation, abbreviated possrep, and explains how these can be used in conjunction with constraints to de

Updating by replacement, Updating by replacement Syntax: UPDAT...

Updating by replacement Syntax: UPDATE ENROLMENT SET Name = 'Ann' WHERE StudentId = SID ('S1'); Note the use of SET, as already noted in connection with direct a

Organic evolution, Organi c Evolution Evolution is a slow continuou...

Organi c Evolution Evolution is a slow continuous, irreversible and natural process of change to give rise to advance and diverse forms of life i.e. formation of new specie

Creating a table, Creating a Table Syantax: CREATE TABLE ENROL...

Creating a Table Syantax: CREATE TABLE ENROLMENT (StudentId SID, Name   VARCHAR (30) NOT NULL, CourseId CID, PRIMARY KEY (StudentId, CourseId)) ; Explan

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