Effects of null for multiple assignments - sql, PL-SQL Programming

Effects of NULL for Multiple Assignments - SQL

If the row expression given as the source for a multiple assignment evaluates to NULL, then NULL is assigned to each target. If a SELECT ... INTO statement results in an empty table, then the target variables are not updated and a completion condition is given to indicate that. This is not exactly an "effect of NULL", of course, but I mention it here because of the contrast with a row subquery, which delivers a single row with NULL for each field when its table expression evaluates to an empty table. This observation might influence the choice between SET and SELECT ... INTO.

Posted Date: 1/18/2013 11:42:01 PM | Location : United States







Related Discussions:- Effects of null for multiple assignments - sql, Assignment Help, Ask Question on Effects of null for multiple assignments - sql, Get Answer, Expert's Help, Effects of null for multiple assignments - sql Discussions

Write discussion on Effects of null for multiple assignments - sql
Your posts are moderated
Related Questions
Exception handling In the PL/SQL, a warning or error condition is known as an exception. The Exceptions can be internally defined (by the run-time system) or user defined. The

JOIN and AND in SQL In this Section is all about one operator, JOIN. SQL's closest counterpart, NATURAL JOIN, has already been covered. Here we look at several other "join" op

Defining REF CURSOR Types To make cursor variables, you take 2 steps. At first, you define a REF CURSOR type, and then declare the cursor variables of that type. You can defin

Initializing Objects: Till you initialize an object by calling the constructor for its object type, the object is automatically null. That is, the object itself is null, not me

First Step at defining type SID in SQL CREATE TYPE SID AS ( C VARCHAR(5) ) ; Explanation: TYPE SID announces that a type named SID is being defined to the syst

Declaring Subprograms   You can declare subprograms in any PL/SQL subprogram, block, or package. But, you should declare subprograms at the end of the declarative part after a

User-Defined Exceptions The PL/SQL defines the exceptions of your own. Dissimilar to the predefined exceptions, the user-defined exceptions should be declared and should be rai

Example of NOT EXISTS Operator - SQL Example is a translation into SQL of the corresponding example, which is included there merely to show that for any scalar comparison the

Explicitly specifying the join condition - SQL SELECT * FROM IS_CALLED JOIN IS_ENROLLED_ON ON ( IS_CALLED.StudentId = IS_ENROLLED_ON.StudentId ) Now, the key word JO

UNION without CORRESPONDING - SQL The use of UNION without CORRESPONDING. Example is merely by omitting CORRESPONDING, but only because the operands have identical SELECT clau