%found - implicit cursor attributes, PL-SQL Programming

%FOUND

Until the SQL data manipulation statement is executed, the %FOUND yields NULL. Afterward, the %FOUND yields TRUE, when an INSERT, UPDATE, or DELETE statement affected one or many rows or a SELECT INTO statement return one or more rows.

Or else, the %FOUND yields FALSE. In the illustration below, you use the %FOUND to insert a row when a delete succeeds:

DELETE FROM emp WHERE empno = my_empno;

IF SQL%FOUND THEN -- delete succeeded

INSERT INTO new_emp VALUES (my_empno, my_ename, ...);

Posted Date: 10/4/2012 4:46:38 AM | Location : United States







Related Discussions:- %found - implicit cursor attributes, Assignment Help, Ask Question on %found - implicit cursor attributes, Get Answer, Expert's Help, %found - implicit cursor attributes Discussions

Write discussion on %found - implicit cursor attributes
Your posts are moderated
Related Questions
Project Description: This is stage 1 of a larger conversion project. We are converting a traditional Server/Client application written in Access 2007 into a web interface with S

Disjunction (OR, ∨) Again we have nine rows instead of just four and again, when unknown is not involved, the rows are as for 2VL. Also, when anything is paired with true, t

Obtaining a natural join by specifying the common columns Synatax: SELECT * FROM IS_CALLED JOIN IS_ENROLLED_ON USING ( StudentId ) However, a named columns join doe

Difference between 9i & 10G When Oracle releases any new databases then it are having some discrepancy with them. But 10G is having much difference than oracle 9i has. Oracle

Create a procedure named STATUS_SHIP_SP that allows a company to employee in the Shipping Department to update the status of an order to add shipping information. The BB_BASKETSTAT

I have a Pascal Source file that needs to be compiled into a Service. In addition, there are various functions (Pascal Procedures I guess) that need to be created to Read and Write

Declaring Records Whenever you define a RECORD type, you may declare records of that type, as the illustration shows: DECLARE TYPE StockItem IS RECORD ( item_no INTEG

Initializing and Referencing Collections Until you initialize a collection, a nested table or varray is automatically null (i.e. the collection itself is null, not its elements)

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,

Many of the reports generated from the system calculate the total dollars in a shopper''s purchases. Follow these steps to create a function named TOT_PURCH_SF that accepts a shopp