Re: Design Help Needed

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 20248
interpreted = N
texte = What would be the benefit to this? I am new to databases so if there is a reason to do it this way, what would it be? I would like to be able to use the quantity of matches in a search to dictate the order in which it displays. more matches = higher on the list of returned records.Could this method be helpful in doing that?- charles >Rather than have separate fields for each one of your options, why not >have one field called OPTIONS and store a separated list of options in >the field. Like the following: 1CarGarage+Basement+SwimPool. I would >maintain the options in a separate database so the codes you store in the >OPTION field are different than the actual names that appear in the HTML >(to prevent the plus sign from being in the name). Thus the option >database might be: > >OPTION_ID OPTION_NAME >1CAR 1 Car Garage >2CAR 2 Car Garage >POOL Swimming Pool >etc. > >Then the option field in your main database would have entries like the >following: > >OPTIONS >1CAR+POOL >2CAR+POOL >1CAR > > >John. > >>I am building a website where people can post homes for sale and search >>for homes. Kind of like realtor.com In my database I have fields for all >>the usual stuff: city state, price, square footage, floors, bedrooms, lot >>size, etc. I also have fields that are more specific and are using check >>boxes like: 1CarGarage, 2CarGarage, Basement, Wooded Lot, Swimming Pool... >> >>My question is what do I store in the database for these later items? My >>initial thought ws to store a T of F whether they have or don't have >>these features. But, I am real new to database design and need some >>advice before I get too deep. >> >>I want the search form to be able to search for all the different >>criteria and show the results in a rated list. Showing the most matches >>first. >> >>let me know what y'all think. >> >>Thanks, >> >>Charles >> >>_______________________________________________________________ >>Charles Kline ckline@macsultants.com >> >> >>MacSultants >>Professional Solutions for Computer Systems >> >>Phone# 609-273-3255 >>Fax# 609-273-3721 > > John A. Hill, V.P. Marketing > Pacific Coast Software >eCommerce / Web Developer Tools > http://www.smithmicro.com > > _______________________________________________________________ Charles Kline ckline@macsultants.com MacSultants Professional Solutions for Computer SystemsPhone# 609-273-3255 Fax# 609-273-3721 Associated Messages, from the most recent to the oldest:

    
  1. Re: Design Help Needed (Rob Marquardt 1998)
  2. Re: Design Help Needed (PCS Technical Support 1998)
  3. Re: Design Help Needed (charles kline 1998)
  4. Re: Design Help Needed (Rob Marquardt 1998)
  5. Re: Design Help Needed (Howard Wolosky 1998)
  6. Re: Design Help Needed (charles kline 1998)
  7. Re: Design Help Needed (charles kline 1998)
  8. Re: Design Help Needed (charles kline 1998)
  9. Re: Design Help Needed (PCS Technical Support 1998)
  10. Re: Design Help Needed (Laurent Pladys 1998)
  11. Design Help Needed (charles kline 1998)
What would be the benefit to this? I am new to databases so if there is a reason to do it this way, what would it be? I would like to be able to use the quantity of matches in a search to dictate the order in which it displays. more matches = higher on the list of returned records.Could this method be helpful in doing that?- charles >Rather than have separate fields for each one of your options, why not >have one field called OPTIONS and store a separated list of options in >the field. Like the following: 1CarGarage+Basement+SwimPool. I would >maintain the options in a separate database so the codes you store in the >OPTION field are different than the actual names that appear in the HTML >(to prevent the plus sign from being in the name). Thus the option >database might be: > >OPTION_ID OPTION_NAME >1CAR 1 Car Garage >2CAR 2 Car Garage >POOL Swimming Pool >etc. > >Then the option field in your main database would have entries like the >following: > >OPTIONS >1CAR+POOL >2CAR+POOL >1CAR > > >John. > >>I am building a website where people can post homes for sale and search >>for homes. Kind of like realtor.com In my database I have fields for all >>the usual stuff: city state, price, square footage, floors, bedrooms, lot >>size, etc. I also have fields that are more specific and are using check >>boxes like: 1CarGarage, 2CarGarage, Basement, Wooded Lot, Swimming Pool... >> >>My question is what do I store in the database for these later items? My >>initial thought ws to store a T of F whether they have or don't have >>these features. But, I am real new to database design and need some >>advice before I get too deep. >> >>I want the search form to be able to search for all the different >>criteria and show the results in a rated list. Showing the most matches >>first. >> >>let me know what y'all think. >> >>Thanks, >> >>Charles >> >>_______________________________________________________________ >>Charles Kline ckline@macsultants.com >> >> >>MacSultants >>Professional Solutions for Computer Systems >> >>Phone# 609-273-3255 >>Fax# 609-273-3721 > > John A. Hill, V.P. Marketing > Pacific Coast Software >eCommerce / Web Developer Tools > http://www.smithmicro.com > > _______________________________________________________________ Charles Kline ckline@macsultants.com MacSultants Professional Solutions for Computer SystemsPhone# 609-273-3255 Fax# 609-273-3721 charles kline

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

frames & carts (1997) Date search - yes or no (1997) searching for items that begin with a number (2004) WebCat2: multiple currency support (1997) Summing fields (1997) Force a search at the default.tmpl page? (1997) Shipping Math (1999) blank orders (2001) WebCatalog can't find database (1997) OT: JavaScript question (2001) sorting dates (1999) [SHOWIF] (1997) Pull Down Search (2000) New Lawsuit Alleges Unitedhealth/Pacificare Deceived (2006) WC Database Format (1997) Generating unique SKU from [cart] - Still Stumped... (1997) taxTotal, too (1997) Still having install problems (2000) Online reference (1997) Talk List Suggestions (1997)