Archives of the TeradataForum
Message Posted: Fri, 30 Jan 2004 @ 15:49:34 GMT
i found the following in the manuals (ALTER TABLE MODIFY CHECK): "This also includes the named constraints defined as part of the column definition since those constraints are handled as named tablelevel constraints."
At least it's documented somewhere...
It's probably because you can MODIFY an existing check and add references to other columns.
So that's why constraintcount for the first column is 0 (no table level checks reference that column).
And it's probably allowed to COMPRESS a value which will not pass the CHECK, because you can MODIFY/DROP the CHECK.
Remember, users do lots of stupid things ;-)
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|