using enum versus tiny int and lookup table
i am looking for some difinitive information on when enum is better to be used compared to using tiny integer and then foreign key to a lookup table. i have many such lookup tables in my database that i believe also could be done with enum. ie months of the year, states of australia, loan types, client types, eg - virtually anything that is a "type" for that matter. despite this seemingly obvious dilemma i can find v little information on the net as to when it is better to use the enum option and when better not to and why. can anyone give a full and clear explanation on this??
Subject
Written By
Posted
using enum versus tiny int and lookup table
April 16, 2008 01:10AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.