One year ago Steven Feuerstein launched a competition called “The Pl/SQL Challenge“.
The idea was to let Oracle PL/SQL developers test their knowledge, learn and win prices by taking a daily quiz.
The format seems to be a success: every day more than 1000 PL/SQL developers test their knowledge about the language, in total more than 5800 users from 119 countries… a worldwide success!
But it does not stop with doing a quiz, a lot of questions(and answers) are discussed on the blog.
And those discussions can also lead to something, like an enhancement request for the PL/SQL language by Bryn Llewellyn(PL/SQL Product Manager at Oracle).
Steven did a great job with the PL/SQL Challenge and it seems like it keeps on rolling: version 2 of the website is coming up with even more challenges for SQL and APEX.
To Steven and his team of reviewers and developers: thanks for the nice quizzes and keep up te great work!
To all players: have fun and good luck!
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 184.108.40.206 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!