Re: Data Design : Numeric or keyword lookup values?

2005-05-09 Thread zzapper
On Sat, 7 May 2005 09:35:21 +0100, wrote: 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.

Re: Data Design : Numeric or keyword lookup values?

2005-05-09 Thread SGreen
news [EMAIL PROTECTED] wrote on 05/06/2005 06:08:18 PM: 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

RE: Data Design : Numeric or keyword lookup values?

2005-05-07 Thread Charles Walmsley
- 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

Data Design : Numeric or keyword lookup values?

2005-05-06 Thread zzapper
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.