Popgun Posted August 6, 2008 Share Posted August 6, 2008 Hello All, Long time lurker, first time poster here. I am currently designing a schema for a project that includes user profiles. So obviously there is a section of the profile that allows for input of demographic information. Ive gotten most every thing normalized but ran into an interesting issue I was hoping someone could help with: Issues: What to do with a gender field? Option A: Make a separate table/field with values: male, female, no answer Height: again male a separate table/field? else there are repeated values much like gender above Weight: I am making a unique table with a "ranges" field? This sound reasonable? Income: Same as above but with "income range" I know that getting to granular on the design leads to performance issues but these particular demographics will be called every time someone loads a profile page so I'd rather design for performance. Thanks in advance! Popgun Quote Link to comment Share on other sites More sharing options...
fenway Posted August 6, 2008 Share Posted August 6, 2008 If you want to do this, use ENUMs. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.