Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> Re: Best practice to corrupt data

Re: Best practice to corrupt data

From: <nospam_at_gojko.com>
Date: 27 Sep 2006 15:23:36 -0700
Message-ID: <1159395816.011662.284470@e3g2000cwe.googlegroups.com>


> debugging. Trying to get a customer to relay the information off of an
> error screen is unrealistic. In fact my experience errors are often

> IMHO -- Mark D Powell --

Hi,

I was not suggesting displaying the oracle stack trace to the client - rather throwing an exception out of the database. End-users should, by all means, get a meaningful error, and the database layer should throw exceptions that are easy to automatically parse and process, so the latter is often just a pointer for the former. I'm sorry if you got the wrong impression, i'll try to explain that better in the blog post.

Gojko Adzic
http://www.gojko.com Received on Wed Sep 27 2006 - 17:23:36 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US