Constraints on views - disable novalidate

From: Peter <peter_at_nomorenewspamin.ca>
Date: Mon, 10 Nov 2003 09:32:20 GMT
Message-ID: <smvtqvcc1k59bi7udlces98ba7urqha71a@4ax.com>

When creating a constraint on views, why is it necessary to include the "disable nonvalidate" keyword?

What is the difference between
"enable novalidate" and "disable validate"?

With the "enable novalidate" constraint, Oracle will not validate existing data but will validate future data. How about changing data of existing rows?

When you create a table with the "disable validate" constraint, does that mean you cannot add any new rows to the table? I cannot see why as Oracle will still validate the existing data, but no new data will be validated.

Does Oracle validate existing data in the table on every DML statement?

Thanks Received on Mon Nov 10 2003 - 03:32:20 CST