On 02/06/2013 13:47, Kevin Grittner wrote:
That's good as far as it goes, but there's another major reason for
wanting the capability. There are cases where, due to dirty
converted data or late recognition of the need for a constraint
there is existing data which violates the constraint. Being
Marko Tiikkaja wrote:
> On 5/27/13 5:23 PM, I wrote:
>> Today I got (unfortunately) reminded that this statement, in
>> sql-altertable.html under VALIDATE CONSTRAINT, is not true anymore:
>>
>> The value of separating validation from initial creation of the
>> constraint is that validation require
On 5/27/13 5:23 PM, I wrote:
Today I got (unfortunately) reminded that this statement, in
sql-altertable.html under VALIDATE CONSTRAINT, is not true anymore:
The value of separating validation from initial creation of the
constraint is that validation requires a lesser lock on the table than
con
Hi,
Today I got (unfortunately) reminded that this statement, in
sql-altertable.html under VALIDATE CONSTRAINT, is not true anymore:
The value of separating validation from initial creation of the
constraint is that validation requires a lesser lock on the table than
constraint creation does