I figured that was what you meant... I guess my table didn't work (see above message...don't ya' love plaintext :-O)...
Has anyone ever tried to benchmark the difference between utilizing ENUMs vs. traditional relational databasing? I would think ENUM is ideal for items I specified at the beginning of this thread, items I would think would be part of MANY (if not MOST) databases (state, country, gender, industry, occupation, referredFrom, ethnicity, position)... In my case, it would allow me to eliminate 15+ tables... I'm just wondering why database ENUMS aren't used more often... (what's the catch) ""Olexandr Melnyk"" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > On Tue, Sep 23, 2008 at 6:13 PM, Olexandr Melnyk <[EMAIL PROTECTED]> > wrote: > >> Plus, if the same query is run very often and table is almost static, >> chances are high that the result will be in query cache. >> > > Just realized that I haven't mentioned that this sentence is related to > storing states in the database, rather than in the application layer. > > -- > Sincerely yours, > Olexandr Melnyk > http://omelnyk.net/ > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
