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
Tags: database, database development, PL/SQL, PL/SQL Challenge, statement restart, Steven Feuerstein
February 28, 2011 at 7:52 am |
Hi Poelger,
Thank you for the effort you put into this question. It was simple and well worded – the hallmarks of a great PL/SQL Challenge question.
I got this question wrong, so I was reminded of something that I should have known from past experience
Well done!
February 28, 2011 at 11:23 am |
The best questions are the ones you learn from. It will be interesting to see if the underlying cause of the restarts is conclusively identified.
March 1, 2011 at 12:23 pm |
Thanks!
Indeed, it’s nice when you have 100% on a question, but it’s more interesting when you learn something and I think a lot of people didn’t know this behaviour(now they do!).
Tom Kyte in his blogpost(http://tkyte.blogspot.com/2010/04/that-old-restart-problem-again.html):
“Why they were restarted – not really relevant – the fact is – they CAN be restarted, we can show that they can be restarted, it is documented that they can be.”
But I’m also a bit curious why it happens.