mysql - Does it still make sense to normalize data (1NF)? (what's wrong with having empty fields in a table?) -


given disk space cheap, make sense normalize data (1nf) rather store in 1 place faster queries?

background:

  1. we have table of users - event organizers , event attendees
  2. both have common fields, organizers have many more fields
  3. attendees far more numerous organizers on site

question: (in far past) combined separate tables existed , made them 1 similar following:

   table_users    uid, name, email, commonfield1, orgspecificfield1, orgspecificfield2 

now, have 1 common table both types of users. attendees, last 2 fields null.

compare above structure to:

   table_users    uid, name, email, commonfield1     table_usersorganizers    uid, orgspecificfield1, orgspecificfield2 

which necessitate join. now, site speed perspective, faster retrieve - common-integrated table or separated one? remember fetching these records.

if talking site speed in fetching data, second choice (the separated table) data retrieving time mainly number of entries in table (number of rows) less in separated ones


Comments

Popular posts from this blog

c# - SharpSVN - How to get the previous revision? -

c++ - Is it possible to compile a VST on linux? -

url - Querystring manipulation of email Address in PHP -