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

Home -> Community -> Mailing Lists -> Oracle-L -> Re: adding a check condition

Re: adding a check condition

From: Gaja Krishna Vaidyanatha <gajav_at_yahoo.com>
Date: Tue, 13 Jun 2000 08:18:07 -0700 (PDT)
Message-Id: <10527.108955@fatcity.com>


Anand,

Vadim is on the money, a constraint is usually a much better performance choice than a trigger for the exact reasons mentioned by him. However, the basic answer to your question is YES, there will be a performance overhead and Rachel has already given you that. But, I am wondering the rationale behind a check constraint for every column to check blanks in data.

Does it makes sense to NOT NULL the columns? What are the various applications that will use these tables? What kind of application is it - client/server, web-based? How much network bandwidth do you have? - this will decide on the amount of application-side data validity checking that needs to be built in. Can you build some of this "blank checking" within the application?

Your question is very simple, but unfortunately the answer is not. There are many facets to the answer and all the issues need to be considered before anything final can be said.

Gaja.

Gaja Krishna Vaidyanatha   | 3460 West Bayshore Road,
Manager - Integration      | Palo Alto, CA 94303
& Consulting Services      | gaja_at_brio.com
Global Alliances           | (650)-565-4442
Brio Technology            | www.brio.com 

"Opinions and views expressed are my own and not of Brio Technology"


Received on Tue Jun 13 2000 - 10:18:07 CDT

Original text of this message

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