ORACLE PL/SQL Exercise (i)

High-performance PL/SQL

Assuming the code meets functional requirements, PL/SQL code needs to meet 3 conditions to become efficient:

1. Performance: The operating time is within an acceptable range.

2. Impact: It does not disrupt (or weaken in some unacceptable way) any other component of your system.

3. Provable: You can prove that, under all reasonable conditions, the code will not break the above performance and then affect. In short, even if you want to be destructive you can't do it.

Using bound variables

SELECT ' &x ' from dual;

Executes a PL/SQL block

BEGIN

Dbms_output. Put_Line (' Hey look,ma! ');

END;

/

Or

exec dbms_output.put_line (' Hey look,ma! ')

This article from "Technology Station" blog, declined reprint!

ORACLE PL/SQL Exercise (i)