On friday my quiz was on the PL/SQL Challenge.
Topic: “Guidelines for Designing Triggers: Avoid Non-Transactional Logic in DML Triggers”
Yes, about “statement restart” :-)
My idea about the quiz was “making developers aware of the Oracle behaviour”.
And I hope a lot of PL/SQL developers learned from it.
It wasn’t easy to come up with the question, the way of asking, the correct words, the answers…
But after a lot of mailing between Steven and the reviewers we finally had a quiz.
A lot people had it wrong, but I hope they don’t mind and are now aware of statement restart.
For more information and discussion about the quiz: PL/SQL Challenge blog
Steven Feuerstein started last year the PL/SQL Challenge, a quiz about…PL/SQL!
What else could one expect from Steven ;-)
The PL/SQL Challenge is an interesting quiz to test your PL/SQL knowledge and win some great prizes(up to $1000!).
Not only it’s about testing your knowledge, but also about learning a lot PL/SQL(even experienced developers can learn!).
At iAdvise and O2U we have some great PL/SQL developers and to prove that: we are the number one company in the PL/SQL challenge in the last quarter of 2010 and leading in this quarter.
We have three players in the top 100 this quarter of which one is in the top 20. And this with over a 1000 participants each day. Not bad I would say.
Not only the experienced players are participating and doing very well, but also our young Apex developers are doing great(one of them was in the beginners top 10 in December).
In the days of Java, E2.0, SOA, Fusion etc… don’t forget the roots: PL/SQL is still the preferred language on the database!
So, come out and play…and maybe win some prizes at the PL/SQL Challenge.
In my previous post I mentioned the problem with compiling a program unit that calls a database function with result cache.
Like I wrote in that post, the problem exists in the PL/SQL Client version.
There’s a patch available to update the PL/SQL client: Oracle Database Server Version 22.214.171.124 Patch 33.
This is a database patch, but it can also be applied to the middleware home.
After applying the patch, the program unit compiles…Problem solved!
So, go and start using Result cache!