[thelist] DB design question

[Ed McCarroll]

Why do you need to put amenities in a separate table.  Couldn't
you have a column for each type of amenity in the main table?

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Ed McCarroll                          MailTo:Ed at ComSimplicity.com
ComSimplicity                                      (310) 838-4330
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

> I'm trying to decide how to
> set up some tables that will describe a property
> listing.  The problem I'm having is deciding what to
> do with descriptions of amenities.  A listing will
> obviously have an address and price in one table but
> what about boolean-type fields such as
> fireplace-yes/no, carpeting-yes/no, etc. of which
> there may be 20 or 30.  I want to be able to search on
> these so how should they be linked back to the main
> table?