Re: Database Structure?

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 19247
interpreted = N
texte = At 23:58 Uhr 31.07.1998, Angel Bennett wrote: -------------------->Client has a database of approx. 6,000 dive gear itemss in a variety of >brands and categories (masks, fins, snorkels, BC's, books, wet-suits, etc.) > >Client wants a user interface that goes like this: Visitor hits Entry.tpl >and is presented with two pull-down menus Search by brand & Search by >Category.No problem. I would generate the popups from data (with the summ parameter). So you do not have to change your code when a category or brand gets added or removed. I suggest to use two different forms for brand-search and category-search, do not allow searching for both at once. Of course, this might add a step in your workflow, but avoids zero-results if the user chooses two nonmatching parameters: there is no mask from MacDonalds, for example. Each form sends the user to a different template to continue: CatSearch.tpl and BrandSearch.tpl - I think one of your [showif]-problems is now solved either...-------------------->If Client chooses say, Masks from the Search by Category >pull-down menu, it will take them to the Search.tpl where they can further >narrow the search by checking boxes of mask brands they're interested in, >weather they have a preference for 2 windows or 4 windows, what kind of >purge system they'd prefer, and what colors they'd like. >... >Okay, that seems normal but here's the catch. In other >categories, or even worse, if the visitor choose to search by brand >initially, the fields may need to be entirely different.That sounds complicated. Do you have such different descriptions in each single category? I cannot find fields for this information in the database-header you posted:>The database I created initial contains the following 24 fields: >SKU, TITLE, PRICE, WEIGHT, BRAND, CATAGORY, TYPE1, TYPE2, TYPE3, SIZE, >SIZECHART, COLOR, SEX, TEMPRANGE, HASIMAGE, IMAGE, HASLIMAGE, LIMAGE, >DESCRIPTION, FEATURES, REPLITEM1, REPLITEM2, OPPADD1, OPPADD2,There are no fields for the special details of the categories.-------------------->1. Can I do it all with the one database?You can. But should you? I do not know yet. Please tell us the number of brands, the number of categories and the individual fields (approximately) for each category.-------------------->2. Do I have enough (or the right) fields to do all the different searches >I need?I don't think so.-------------------->3. Is it possible to use *that many* [showif] tags without ridiculous >slow-downs?[showif]'s do not necessarily slow you down so much.-------------------- Peter__________________________________________ Peter Ostry - po@ostry.com - www.ostry.com Ostry & Partner - Ostry Internet Solutions Auhofstrasse 29 A-1130 Vienna Austria fon ++43-1-8777454 fax ++43-1-8777454-21 Associated Messages, from the most recent to the oldest:

    
  1. Re: Database Structure? (Angel Bennett 1998)
  2. Re: Database Structure? (Peter Ostry 1998)
  3. Re: Database Structure? (Angel Bennett 1998)
  4. Re: Database Structure? (Angel Bennett 1998)
  5. Re: Database Structure? (Peter Ostry 1998)
  6. RE: Database Structure? (Pat McCormick 1998)
  7. Database Structure? (Angel Bennett 1998)
  8. Re: Database Structure? (Peter Ostry 1998)
At 23:58 Uhr 31.07.1998, Angel Bennett wrote: -------------------->Client has a database of approx. 6,000 dive gear itemss in a variety of >brands and categories (masks, fins, snorkels, BC's, books, wet-suits, etc.) > >Client wants a user interface that goes like this: Visitor hits Entry.tpl >and is presented with two pull-down menus Search by brand & Search by >Category.No problem. I would generate the popups from data (with the summ parameter). So you do not have to change your code when a category or brand gets added or removed. I suggest to use two different forms for brand-search and category-search, do not allow searching for both at once. Of course, this might add a step in your workflow, but avoids zero-results if the user chooses two nonmatching parameters: there is no mask from MacDonalds, for example. Each form sends the user to a different template to continue: CatSearch.tpl and BrandSearch.tpl - I think one of your [showif]-problems is now solved either...-------------------->If Client chooses say, Masks from the Search by Category >pull-down menu, it will take them to the Search.tpl where they can further >narrow the search by checking boxes of mask brands they're interested in, >weather they have a preference for 2 windows or 4 windows, what kind of >purge system they'd prefer, and what colors they'd like. >... >Okay, that seems normal but here's the catch. In other >categories, or even worse, if the visitor choose to search by brand >initially, the fields may need to be entirely different.That sounds complicated. Do you have such different descriptions in each single category? I cannot find fields for this information in the database-header you posted:>The database I created initial contains the following 24 fields: >SKU, TITLE, PRICE, WEIGHT, BRAND, CATAGORY, TYPE1, TYPE2, TYPE3, SIZE, >SIZECHART, COLOR, SEX, TEMPRANGE, HASIMAGE, IMAGE, HASLIMAGE, LIMAGE, >DESCRIPTION, FEATURES, REPLITEM1, REPLITEM2, OPPADD1, OPPADD2,There are no fields for the special details of the categories.-------------------->1. Can I do it all with the one database?You can. But should you? I do not know yet. Please tell us the number of brands, the number of categories and the individual fields (approximately) for each category.-------------------->2. Do I have enough (or the right) fields to do all the different searches >I need?I don't think so.-------------------->3. Is it possible to use *that many* [showif] tags without ridiculous >slow-downs?[showif]'s do not necessarily slow you down so much.-------------------- Peter__________________________________________ Peter Ostry - po@ostry.com - www.ostry.com Ostry & Partner - Ostry Internet Solutions Auhofstrasse 29 A-1130 Vienna Austria fon ++43-1-8777454 fax ++43-1-8777454-21 Peter Ostry

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:

Unix DB Permission Error (2002) WebCatalog2 Feature Feedback (1996) emailer (1997) Simple Store (2000) [Announce] Newest Commerce Site based on WebCatalog (1997) [AppendFile] problem (WebCat2b13 Mac .acgi) (1997) [SearchString] problem with [search] context (1997) Using [sendmail] for mass mailings (2001) Implementing Gift Certificates in online store (1998) windows v4.5.1 (2003) Lost and Recovered. (1998) Questions about maximum (1999) Re:Change WebDNA-Talk Mail due to no digest for 1wk (1997) URL for Discussion Archive (1997) WCS Newbie question (1997) Shipping costs question (2002) Formvariables + Netscape + Frame Set = Confusion (2000) ASCII Code 127 (2004) PCS Frames-Default page is solution! (1997) [WebDNA] SQLExecute Memory Leak (2008)