Archives of the TeradataForum
Message Posted: Mon, 26 Jan 2004 @ 19:04:10 GMT
I have created a table with column constraints: V2R4.1.3
CREATE SET TABLE mvanole.columnconst ,NO FALLBACK , NO BEFORE JOURNAL, NO AFTER JOURNAL ( c29b CHAR(2) CHARACTER SET LATIN NOT CASESPECIFIC NOT NULL CHECK ( ("c29b" = 'y') OR ("c29b" = 'n') ), c29a CHAR(1) CHARACTER SET LATIN NOT CASESPECIFIC NOT NULL COMPRESS 'Y' CONSTRAINT MYCONST2 CHECK ( ("c29a" = 'y') OR ("c29a" = 'n') ), c29c CHAR(1) CHARACTER SET LATIN NOT CASESPECIFIC NOT NULL COMPRESS 'x' CONSTRAINT MYCONST3 CHECK ( ("c29c" = 'y') OR ("c29c" = 'n') ) ) PRIMARY INDEX (c29b);
When I do HELP COLUMN * from MVANOLE.COLUMNCONST the named contraints do no show up. Nor do they appear in dbc.columns. Also, dbc.columns.constraintcount has a 0, and for the two named contraint columns there is a 1. Shouldn't I expect 1's for all three columns?
Only when I do HELP CONSTRAINT mvanole.columnconst.myconst2; will I be able to see the actual contraint. It seems to me that I should see all contraints with HELP COLUMN or from dbc.columns. Is this a bug? V2R5.0 behaves the same way.
Also notice that I can specify COMPRESS 'x' when my constraint is for 'Y' or 'N'. I would expect an error for this conflict.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|