Oracle updating cursor loop

Static cursors are used only for DML statements (SELECT, INSERT, UPDATE, DELETE, MERGE, or SELECT FOR UPDATE).

These static cursors can be explicitly declared and named or may appear in-line as an implicit cursor.

All procedural code is handled by the PL/SQL engine while all SQL is handled by the SQL statement executor, or SQL engine.

There is an overhead associated with each context switch between the two engines.

Oracle generously provides a list of things developers can do to tune their PL/SQL code.

One item from that list is probably the single best tool developers have at their disposal to supercharge their code: bulk processing.

With PL/SQL you have more control over what happens when exceptions occur.

SQL courses meet the most demanding needs of the business world for advanced education in a cost-effective manner.

For UPDATE and DELETE operations, the cursor identifies the rows that would be affected.In this chapter, we will discuss the cursors in PL/SQL. A cursor holds the rows (one or more) returned by a SQL statement.Oracle creates a memory area, known as the context area, for processing an SQL statement, which contains all the information needed for processing the statement; for example, the number of rows processed, etc. The set of rows the cursor holds is referred to as the active a name assigned to a specific private SQL area for a specific SQL statement.There can be either static cursors, whose SQL statement is determined at compile time, or dynamic cursors, whose SQL statement is determined at runtime.

Leave a Reply