RE: DDL Specs

Those values will not ever change.....and there is no possibility that we
will add additional values.....but I see your point and if those were
possibilities I would agree with you......actually in 99.9% of all cases I
could agree :)

I am in an agreeable mood today.......




From:
<lgoodbar@xxxxxxxxxxxxxx>
To:
<midrange-l@xxxxxxxxxxxx>
Date:
05/30/2008 10:13 AM
Subject:
RE: DDL Specs



The best way is to define that lookup table separately and populate with
values C, V, and U. Then use referential integrity (foreign key
constraint) on the other table to restrict values. That way the lookup
table can be updated without changing the dependant table.

Loyd Goodbar
Business Systems
BorgWarner Shared Services
662-473-5713
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Doug Palme
Sent: Friday, May 30, 2008 9:21 AM
To: Midrange Systems Technical Discussion
Subject: DDL Specs

I have been going through the SQL reference guide looking for some help
on
restricting the values that can be entered into a table. I would like
to
put this constraint on the file from within the DDL is possible.....so
far
I have been unable to figure it out.

Example: I have a 1A field that can only have a value of 'C', 'V' or
'U',
no other values will be allowed.....is there a way to include this
within
the DDL?