Pokemon and When Others...
Question: What do Pokemon and When Others in PL/SQL have in common?
For many developers the answer is:
Asnwer: You gotta catch 'em all.
I saw this other blog post on "Dodgy Coder" and was greatly amused by the comparison of Pokemon and catching all exceptions and basically making them disappear.
I've written about this "worst" practice a lot. You can see some of them at:
You really DON'T gotta catch em' all! And if you do - you really gotta throw them again (re-raise them)
For many developers the answer is:
Asnwer: You gotta catch 'em all.
I saw this other blog post on "Dodgy Coder" and was greatly amused by the comparison of Pokemon and catching all exceptions and basically making them disappear.
I've written about this "worst" practice a lot. You can see some of them at:
- http://tkyte.blogspot.com/2007/03/dreaded-others-then-null-strikes-again.html
- http://tkyte.blogspot.com/2008/06/when-others-then-null-redux.html
- http://www.oracle.com/technetwork/issue-archive/2007/07-jul/o47asktom-092692.html
- http://www.oracle.com/technetwork/issue-archive/2011/11-nov/o61asktom-512015.html (why you really want to let exceptions propagate)
You really DON'T gotta catch em' all! And if you do - you really gotta throw them again (re-raise them)
posted by Thomas Kyte at 8:12 AM
3 Comments:
see the comic:
http://trenchescomic.com/comic/post/infiltrator
then read the article:
http://trenchescomic.com/tales/post/sql-injection
interested to hear the response
@Unknown,
both are close enough to reality to be real... Especially the sql injection one - I'm pretty sure stuff like that happens just about every second somewhere.
It turns out that Oracle 'developers' are not the only people prone to when others then null.
http://blogs.computerworld.com/20257/but_i_finally_got_it_to_run_clean
POST A COMMENT
<< Home