in reply to database design issue: one big table vs hundred of smaller tables

You should look to normalization for each of your catagories. For instance, the kids/grown_ups split dupes information in the birth date field of each. Kids are constantly filtering into the grown-up side of the ledger. Unifying that classification to just Persons will let you select by whatever age range is desired, without maintainance of redundant categories.

After Compline,
Zaxo

  • Comment on Re: database design issue: one big table vs hundred of smaller tables