Begin parameter description in pl sql, PL-SQL Programming

BEGIN Parameter Description in pl sql:

BEGIN:

This keyword signals the beginning of the executable section of a PL/SQL block, that contains executable statements. The executable section of a block is needed. That is, the PL/SQL block should contain at least one executable statement. The NULL statement meets this necessity.

Statement:

This is an executable (that is not declarative) statement which you use to create the algorithms. A series of statements can involve the procedural statements like RAISE, SQL statements like the UPDATE, and PL/SQL blocks (sometimes known as the "block statements").

The PL/SQL statements are free format. That is, they can continue from line to line if you do not crack keywords, delimiters, or literals across the lines. A semicolon (;) serve as the statement terminator.

The PL/SQL supports a subset of the SQL statements which involves the cursor control, data manipulation, and transaction control statements but exclude the data definition and data control statements like CREATE, ALTER, GRANT, and REVOKE.

EXCEPTION:

This keyword signals the beginning of the exception-handling section of the PL/SQL block. When an exception is raised, the normal execution of the block stops and control transfers to the suitable exception handler. After the exception handler complete, the execution proceeds with the statement following the block.

If there is no exception handler for the raised exception in the present block, the control passes to the enclosing block. This process repeat until an exception handler is found or there are no more enclosing blocks. If the PL/SQL can find no exception handler for the exception, the execution stops and an unhandled exception error is returned to the host atmosphere.

exception_handler:

This construct relates an exception with a series of statements that is executed when the exception is raised.

END:

This keyword signals the end of the PL/SQL block. It should be the last keyword in a block. Neither the END IF in an IF statement nor the END LOOP in a LOOP statement can replace for the keyword END. The END does not signal the end of a transaction. Merely as a block can span the multiple transactions, a transaction can span the multiple blocks.

Posted Date: 10/6/2012 8:56:33 AM | Location : United States







Related Discussions:- Begin parameter description in pl sql, Assignment Help, Ask Question on Begin parameter description in pl sql, Get Answer, Expert's Help, Begin parameter description in pl sql Discussions

Write discussion on Begin parameter description in pl sql
Your posts are moderated
Related Questions
Order of Evaluation When you do not use the parentheses to specify the order of evaluation, the operator precedence determine the order. Now compare the expressions below: NOT

We are seeking a freelance consultant that is familiar with Appgen applications. We require exporting all our data into a format appropriate for importing into SAP Business One. Pl

Pl/SQL Expressions The Expressions are constructed by using the operands and operators. An operand is a constant, literal, variable, or function call which contributes a value

Declaring and Initializing Objects: An object type is once defined and installed in the schema; you can use it to declare the objects in any PL/SQL, subprogram, block or packa

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

Keyword and Parameter Description: label_name: This is an undeclared identifier which optionally labels the PL/SQL block. When used, label_name should be enclosed by the do

Using Host Arrays The Client-side programs can use anonymous PL/SQL blocks to bulk-bind input and output host arrays. However, this is the well-organized way to pass the colle

Existential Quantification - SQL Existential quantification-stating that something is true of at least one object under consideration-can be expressed by OR(r,c), meaning tha

Named Notation The second procedure call uses the named notation. An arrow (=>) serve as the relationship operator that associates the formal parameter to the left of the arro

Table Comparison - SQL The following definitions for relation comparisons: Let r1 and r2 be relations having the same heading. Then: r1 ⊆ r2 is true if every tuple of r1