BI
Now this is how to post a truly technical blog entry. One sentence of English at the start, one at the end, the rest is code: Bursting: Conditional delivery at the BI Publisher developer blog. A few less words and the blog would be entirely machine readable.
RDBMS
Ok, this next one, unlike the BI posting above, this posting over at the Database Geek Blog has a whole paragraph up front before it goes into code: Use a Pipelined Function to Select Source Code Arguments.
also in the realm of PL/SQL and more generally in the realm of logic is Eddie Awad's posting (with links to Tom Kyte) on Why WHEN OTHERS THEN RAISE Can Be Harmful.
And finally a nice article on Miladin Modrakovic's Blog: Oraclue on Detecting Deadlock Source (Part 1). Once again, almost all code, and very useful code at that. You can use his example to set up a deadlock and then try a variety of tools to see how well they do on tracking it down.
2 comments:
Your URL for the Eddie Awad article is actually a duplicate of the previous Database Geek link.
Cheers, APC
I'm glad that someone is paying attention. Possibly not me. Thanks! I fixed it.
Post a Comment