PLSQL Notes From 3 day course in Turkcell Academy

Last week, I had a chance to be author of PLSQL course in Turkcell Academy.

Following issues worth noting which were a product of focused working/reading, nearly for a month, on PL/SQL topic:

-If you handle the exception fired by error RAISE_APPLICATION_ERROR in a BEFORE INSERT trigger body, it is surprising that the record is inserted despite the error message which is shown by RAISE_APPLICATION_ERROR.

- It is also strange that, if you want to prevent truncate table statements with a trigger. Although it is not executed, it will issue COMMIT implicitly because truncate statement is DDL.

http://hemantoracledba.blogspot.com/2011/06/ddl-triggers.html

 

- In order to get use of 11G fine grained dependency feature, thus not to invalidate procedures, views when exactly not needed, in sql statements you must reference underlying table columns with fully qualified names.

http://htmldb.oracle.com/pls/otn/f?p=2853:4:830114251864401::NO::P4_QA_ID:15642

HP returns the Oracle game

Despite the dbas murmuring about Oracle working on HPUX,it seems unfair a vendor is disqualified after years of contribution to Oracle technology.

And good news, HP wins the Itanium lawsuit against Oracle.

http://allthingsd.com/20120801/hp-wins-key-ruling-in-itanium-lawsuit-with-oracle/?mod=googlenews

Why PLSQL is efficient than any other PL on Oracle database?

12 years ago when I argued on the performance of  Programming Languages with an experienced Java programmer, who was developing CORBA like communication infrastructure and preferring only Java, confessed that a dba might develop better performance code than him in PLSQL.

In Turkish, there is a saying "tools work, hands take pride on".  So why not use PLSQL much more...

PLSQL is really on database and closer to database layer any other Programming Languae could manage to be .

After years passed, using SQL instead of PLSQL was my first goal while implementing any requirement.

I had first seen below statement nearly 1 year ago, and it really fit my thoughts which I have not been clearly stated before. I really appreciated it and compelled to get my knowledge world.

My mantra, that I'll be sticking with thank you very much, is:

• You should do it in a single SQL statement if at all possible.


• If you cannot do it in a single SQL Statement, then do it in PL/SQL.


• If you cannot do it in PL/SQL, try a Java Stored Procedure.


• If you cannot do it in Java, do it in a C external procedure.


• If you cannot do it in a C external routine, you might want to seriously think about why it is you need to do it…

http://tkyte.blogspot.com/2006/10/slow-by-slow.html