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: Oracle 9i View's Primary Key constraint

Re: Oracle 9i View's Primary Key constraint

From: HansF <News.Hans_at_telus.net>
Date: Fri, 20 Jan 2006 02:45:29 GMT
Message-Id: <pan.2006.01.20.02.45.26.569449@telus.net>


[After 75 seconds of searching,] from the 10g R2 Concepts manual (newer than 9i and presumably a superset of capabilities), in Chapter 5, I read

"
Only logical constraints, that is, constraints that are declarative and not enforced by Oracle, can be defined on views. The purpose of these constraints is not to enforce any business rules but to identify multidimensional data. The following constraints can be defined on views:

Given that view constraints are declarative, DISABLE, NOVALIDATE is the only valid state for a view constraint. However, the RELY or NORELY state is also allowed, because constraints on views may be used to enable more sophisticated query rewrites; a view constraint in the RELY state allows query rewrites to occur when the rewrite integrity level is set to trusted mode.

Note: Although view constraint definitions are declarative in nature, operations on views are subject to the integrity constraints defined on the underlying base tables, and constraints on views can be enforced through constraints on base tables.
"

http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14220/schema.htm#sthref858

-- 
Hans Forbrich                           
Canada-wide Oracle training and consulting
mailto: Fuzzy.GreyBeard_at_gmail.com   
*** Top posting [replies] guarantees I won't respond. ***
Received on Thu Jan 19 2006 - 20:45:29 CST

Original text of this message

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