One issue you have to consider is how the data is entered. If the user selects from a drop down list then this is ok but you need to plan how the drop down list is compiled. If not then you need to thinks about spelling errors, language issues etc.
Charles Walmsley -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of zzapper Sent: 06 May 2005 23:08 To: mysql@lists.mysql.com Subject: Data Design : Numeric or keyword lookup values? hi, When designing data it is common to have lookup tables such animal_type : dog=1, cat=2,bird=3 etc And then in other tables to refer to animals by their number 1, 2 or 3. This is memory and presumably speed efficient. Howver not much fun for humans who are "reading/debugging" the data. Alternatively it's possible to have a lookup table containing animal types as text strings "cat" "dog", "bird" and actually then use the actual "names" where ever required in other tables. If table size & speed are not top priority is there anything wrong with using 2nd method? Views/opinions please -- zzapper vim -c ":%s%s*%Cyrnfr)fcbafbe[Oenz(Zbbyranne%|:%s)[[()])-)Ig|norm Vg?" http://www.rayninfo.co.uk/tips/ vim, zsh & success tips -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
