design question - several related variables - in one database field or separate fields

[NotGiven]

Say you want to display and search "services offered". There are a finite
number of services offered. You want to be able to search the database for
each service offered separately.

Given the above requirements, is it better to group them in one field and do
a LIKE % query or have each a seprarte database field?

I think separate fields but want opinions as I am somewhat new to this.

Thanks!

[Herbie Cumberland]

On Fri, 23 Jul 2004 16:36:59 -0400, "NotGiven" <no****@nonegiven.net>
wrote:

Say you want to display and search "services offered". There are a finite
number of services offered. You want to be able to search the database for
each service offered separately.

Given the above requirements, is it better to group them in one field and do
a LIKE % query or have each a seprarte database field?

I think separate fields but want opinions as I am somewhat new to this.

Thanks!

if it's a finite number then use seperate fields.

if the possibilities are YES or NO for each service then use binary
fields (1 or 0) - eg. INT(1), CHAR(1) or something like that - this
will speed up searches considerably (as long as you remember to index
all the fields you will be including in your 'WHERE' statement).

[NotGiven]

good advice - thanks
"Herbie Cumberland" <sp******@skipraider.com> wrote in message
news:f3********************************@4ax.com...

On Fri, 23 Jul 2004 16:36:59 -0400, "NotGiven" <no****@nonegiven.net>
wrote:

Say you want to display and search "services offered". There are a finitenumber of services offered. You want to be able to search the database foreach service offered separately.

Given the above requirements, is it better to group them in one field and doa LIKE % query or have each a seprarte database field?

I think separate fields but want opinions as I am somewhat new to this.

Thanks!

if it's a finite number then use seperate fields.

if the possibilities are YES or NO for each service then use binary
fields (1 or 0) - eg. INT(1), CHAR(1) or something like that - this
will speed up searches considerably (as long as you remember to index
all the fields you will be including in your 'WHERE' statement).