By ga79820
via orafaq.com
Published: Sep 25 2006 / 17:37
A common practice for handling errors in PL/SQL procedures is to catch all errors in the top-most database layer and convert them into error codes and human readable messages for client applications. This technique is a relict from the past and, in fact, a very bad practice from today's perspective, since it can lead to data corruption.
-
Patch3 for NetBeans IDE 6.1 Now Available
-
Custom Collections with NHibernate, Part IV: Extensions!
-
CSS-Tricks Video Screencast #34: Integrating and Customizing Google Maps
-
What You Need to Know About Improving the User Experience
-
Modal Popup Extender, AJAX Tool Kit, Validation Controls ASP.NET
-
Language-Based Interfaces, Part 2: Where do we stand now?
Comments
kayess replied ago:
At first glance I thought this was going to offer some terrible advice, but actually it's pretty good.
What I don't understand though is that anybody thought that destroying the error handling in the SQL server was a good idea. That anybody *still* believes that beggars belief!
Voters For This Link (10)
Voters Against This Link (0)