RE: Restricting the range of values in a field

> please remember us when the list of "2-to-5 values that never change"
> change. and we tell you "we told you so".
>
> and why do you care if the developer will get mad? he's wrong. you
know, I
> know it and everyone on this list knows it.
>
> foreign keys are the final answer.
>
> that is all.

In the main, I absolutely agree (i.e. I don't think lookup tables are inherently "bad").

However, in this particular instance, the check constraint is a perfect solution (I won't bore you with the reasons why).

-- 
Aidan Whitehall <aidanwhitehall_at_fairbanks.co.uk>
Macromedia ColdFusion Developer
Fairbanks Environmental Ltd  +44 (0)1695 51775

________________________________________________________________________
This e-mail has been scanned for all viruses by Star Internet. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________
-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Aidan Whitehall
  INET: AidanWhitehall_at_Fairbanks.co.uk

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).