Already have an account? Get multiple benefits of using own account!
Login in your account..!
Remember me
Don't have an account? Create your account in less than a minutes,
Forgot password? how can I recover my password now!
Enter right registered email to receive password!
Assigning and Comparing CollectionsOne collection can be assigned to other by an SELECT, INSERT, UPDATE, or FETCH statement, an assignment statement, or by a subprogram call. As the illustration shown below, the collections should have the same datatype. Having the similar element type is not enough.DECLARETYPE Clientele IS VARRAY(100) OF Customer;TYPE Vips IS VARRAY(100) OF Customer;group1 Clientele := Clientele(...);group2 Clientele := Clientele(...);group3 Vips := Vips(...);BEGINgroup2 := group1;group3 := group2; -- illegal; Various datatypes becomes automatically null (and should be reinitialized). Now consider the illustration as shown below: DECLARETYPE Clientele IS TABLE OF Customer;group1 Clientele := Clientele(...); -- initializedgroup2 Clientele; -- atomically nullBEGINIF group1 IS NULL THEN ... -- condition yields FALSEgroup1 := group2;IF group1 IS NULL THEN ... -- condition yields TRUE...END;Similarly, if you assign the non-value NULL to a collection, the collection becomes automatically null.Assigning Collection ElementsYou can assign the value of an expression to the specific element in a collection by using the syntaxcollection_name(subscript) := expression;Where the expression yields a value of the type specified for elements in the collection type definition. If the subscript is null or not convertible to an integer, the PL/SQL raises the predefined exception VALUE_ERROR. If the collection is automatically null, then the PL/SQL raises COLLECTION_IS_NULL. Some of the examples are shown below:DECLARETYPE NumList IS TABLE OF INTEGER;nums NumList := NumList(10,20,30);ints NumList;...BEGIN...nums(1) := TRUNC(high/low);nums(3) := nums(1);nums(2) := ASCII(’B’);/* Assume execution continues despite the raised exception. */nums(’A’) := 40; -- raises VALUE_ERRORints(1) := 15; -- raises COLLECTION_IS_NULLEND;Comparing Whole CollectionsThe Nested tables and varrays can be automatically null; therefore they can be tested for the nullity, as the example below shows:DECLARETYPE Staff IS TABLE OF Employee;members Staff;BEGIN...IF members IS NULL THEN ... -- condition yields TRUE;END;Though, the collections cannot be compared for equality or inequality. For illustration, the IF condition below is illegal as shown:DECLARETYPE Clientele IS TABLE OF Customer;group1 Clientele := Clientele(...);group2 Clientele := Clientele(...);BEGIN...IF group1 = group2 THEN -- causes compilation error...END IF;END;This restriction also applies to implicit the comparisons. For illustration, the collections cannot appear in an ORDER BY, GROUP BY, or DISTINCT list.
EXECUTE IMMEDIATE Statement The EXECUTE IMMEDIATE statement prepare (parses) and instantly executes a dynamic SQL statement or an anonymous PL/SQL block. Syntax:
Avoid the NOT NULL Constraint In the PL/SQL, using the NOT NULL constraint incur a performance cost. Consider the illustration as shown below: PROCEDURE calc_m IS m NUMB
SSRS Report Writing Project Description: This report is part of a larger project to make a SQL Server Reporting Service (SSRS) based reporting solution. There can be more rep
Create a Oracle procedure to produce vertical output format when selecting rows from a database table.
Using research notes and Oracle documentation plan and execute an upgrade of an installation of Oracle 10g to Oracle 11g release 1. To do this you must show in screen shots and wri
Manipulating Individual Elements Faraway you have manipulated an entire collection. Within the SQL, to manipulate the individual elements of the collection, and then use the ope
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
Package Body: The package specification is implemented by the package body. That is, the package body has the definition of every cursor and the subprogram declared in the pac
Autonomous versus Nested Transactions Though an autonomous transaction is started by the other transaction, it is not a nested transaction for the reasons shown below: (i)
BETWEEN and NOT BETWEEN Operator in SQL Example: Restricting exam marks to between 0 and 100 CREATE ASSERTION Marks_between_0_and_100 CHECK (NOT EXISTS (SELECT * FROM
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!
whatsapp: +91-977-207-8620
Phone: +91-977-207-8620
Email: [email protected]
All rights reserved! Copyrights ©2019-2020 ExpertsMind IT Educational Pvt Ltd