Re: Database Structure?
This WebDNA talk-list message is from 1998
It keeps the original formatting.
numero = 19294
interpreted = N
texte = Peter & Ken, thank you both so much for your detailed responses!!!! Here is are my counter questions:At 10:17 PM 7/31/98, you wrote: >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...That's what I was thinking; two different forms would add an extra step but probably save me from a huge messy file.>>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,The DESCRIPTION field contains a paragraph of descriptive text. FEATURES lists key elements and TYPE1, TYPE2, & TYPE3 are for subcategorizing. For example, in the Regulators Category, TYPE 1 will show if the item is piston or diaphragm. TYPE 2 will show the # of LP ports. TYPE 3 will show the # of HP ports. Then in the DESCRIPTION and/or FEATURES fields it will say whether or not the product is adjustable or nonadjustable, balanced or non-balanced.In the Lights category, TYPE 1 will show if the item is Halogen, Xenon, or Strobe TYPE2, & TYPE3 will always be blank because there is no further subcategorizing. See what I mean about tricky?At 10:17 PM 7/31/98, I originally asked: >1. Can I do it all with the one database?Peter says: 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. Ken says: Yes.In anser to Peter's request that I post the # of brands, the # of categories & the individual fields for each category, I'll try but the database is being buit right now. (All the client gave us was a database containing; sku, brand, title, price, and weight)There are approx. 17 different brands. Some have products in all catagories, most make products in a only a few.There are approx 11 catagories and these are the fields for each:Suits - TYPE1 full/half suit, TYPE2 wet/dry, TYPE3 sock/vest/hood, SIZE=s,m,l,xl, SIZECHART is a link to a size chart, COLOR, SEX, & TEMPRANGE are all applicable, HASIMAGE=T, IMAGE, HASLIMAGE=Sometimes, LIMAGE, DESCRIPTION is a paragraph of text, FEATURES is a list, REPLITEM1, REPLITEM2, OPPADD1 & OPPADD2 all apply to a few in this catagory Computers - TYPE1 metric/imperial, TYPE2 PC download/nitrox, TYPE3 hosesless/air-integrated, SIZE, SIZECHART, COLOR, SEX, & TEMPRANGE do not not apply, HASIMAGE=T, IMAGE, HASLIMAGE=Sometimes, LIMAGE, DESCRIPTION is a paragraph of text, FEATURES is a list, REPLITEM1, REPLITEM2, OPPADD1 & OPPADD2 all apply to a few in this catagoryLights - TYPE1 halogen/xenon/strobe, TYPE2 wattag, TYPE3 blank, SIZE is in inches, SIZECHART, COLOR, & SEX do not not apply, TEMPRANGE is used for wattage, HASIMAGE=T, IMAGE, HASLIMAGE=Never, LIMAGE, DESCRIPTION is a paragraph of text, FEATURES is a list, REPLITEM1, REPLITEM2, OPPADD1 & OPPADD2 all apply to a few in this catagoryAcceories - has 16 subcatagories that are named in the TYPE 1 field, TYPE2, & TYPE3 are blank, SIZE may be in ounces, inches, feet, or S,M,L, SIZECHART, SEX, & TEMPRANGE do not not apply, COLOR applies to some, HASIMAGE=T, IMAGE, HASLIMAGE=Sometimes, LIMAGE, DESCRIPTION is a paragraph of text, FEATURES is a list, REPLITEM1, REPLITEM2, OPPADD1 & OPPADD2 none applyDo you really want me to go through all eleven? okay.Watches - TYPE1 waterproof/water resistant, TYPE2 & TYPE3 are blank SIZE, SIZECHART, & COLOR do not not apply, but SEX does, and TEMPRANGE is used instead for depth rating, and HASIMAGE=T, IMAGE, HASLIMAGE=Sometimes, LIMAGE, DESCRIPTION is a paragraph of text, FEATURES is a list, REPLITEM1, REPLITEM2, OPPADD1 & OPPADD2 all apply to a few in this catagoryWatertight Cases - TYPE1, TYPE2 & TYPE3 are blank, SIZE is in square inches, SIZECHART, & COLOR do not not apply, but SEX does, and TEMPRANGE is used instead for depth rating, and HASIMAGE=T, IMAGE, HASLIMAGE=Never, LIMAGE, DESCRIPTION is a paragraph of text, FEATURES is a list, REPLITEM1, REPLITEM2, OPPADD1 & OPPADD2 all apply to a few in this catagoryOdds and Ends - has 12 subcatagories that are named in the TYPE 1 field, TYPE2, & TYPE3 are blank, SIZE may be in ounces, inches, feet, or S,M,L, or not applicable SIZECHART, SEX, & TEMPRANGE do not not apply, COLOR applies to some, HASIMAGE=T, IMAGE, HASLIMAGE=never, LIMAGE, DESCRIPTION is a paragraph of text, FEATURES is a list, REPLITEM1, REPLITEM2, OPPADD1 & OPPADD2 none applyPhotography - has 5 subcatagories that are named in the TYPE 1 field, TYPE2, & TYPE3 are blank, SIZE, SIZECHART, SEX, TEMPRANGE, COLOR do not not apply, HASIMAGE=T, IMAGE, HASLIMAGE=Never, LIMAGE, DESCRIPTION is a paragraph of text, FEATURES is a list, REPLITEM1, REPLITEM2, OPPADD1 & OPPADD2 some applyReels - TYPE1, TYPE2 & TYPE3 are blank, SIZE reffers to lenght of line in feet or inches, SIZECHART, COLOR, SEX, & TEMPRANGE do not not apply, and HASIMAGE=T, IMAGE, HASLIMAGE=Never, LIMAGE, DESCRIPTION is a paragraph of text, FEATURES is a list, REPLITEM1, REPLITEM2, OPPADD1 & OPPADD2 some apply Guns - has 5 subcatagories that are named in the TYPE 1 field, TYPE2, & TYPE3 are blank, SIZE reffers to shaft lenght in feet, SIZECHART, SEX, TEMPRANGE, COLOR do not not apply, HASIMAGE=T, IMAGE, HASLIMAGE=Never, LIMAGE, DESCRIPTION is a paragraph of text, FEATURES is a list, REPLITEM1, REPLITEM2, OPPADD1 & OPPADD2 some applyEducation - has 4 (books, CD-ROMS, etc.) subcatagories that are named in the TYPE 1 field, TYPE2 list the further subcatagories or subjet headers, & TYPE3 is the author, SIZE reffers to # of pages, SIZECHART, SEX, TEMPRANGE, & COLOR do not not apply, HASIMAGE=T, IMAGE, HASLIMAGE=Never, LIMAGE, DESCRIPTION is a paragraph of text, FEATURES is a list, REPLITEM1, REPLITEM2, OPPADD1 & OPPADD2 none applyWHEW!!!My next question were: >2. Do I have enough (or the right) fields to do all the different searches >I need? Peter: I don't think so. Ken: I think so.>3. Is it possible to use *that many* [showif] tags without ridiculous >slow-downs? Peter:
Ken: Yes.>4. If it *would* be better to do multiple databases, say one for each >brand, how do I do a search calling up all the catagories listed in all the >databases? Peter: Ken: It is NOT better to split the db. If you do, you will be sorry later ...:( Does my somewhat brief description of the fields in each catagory make it more clear if I should split up the database?Angel J. Bennett ! We want the world and VP / Creative Dir. ! we want it... The WWW Store ! NOW! 818-905-6787 ! http://www.thewwwstore.com
Associated Messages, from the most recent to the oldest:
Peter & Ken, thank you both so much for your detailed responses!!!! Here is are my counter questions:At 10:17 PM 7/31/98, you wrote: >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...That's what I was thinking; two different forms would add an extra step but probably save me from a huge messy file.>>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,The DESCRIPTION field contains a paragraph of descriptive text. FEATURES lists key elements and TYPE1, TYPE2, & TYPE3 are for subcategorizing. For example, in the Regulators Category, TYPE 1 will show if the item is piston or diaphragm. TYPE 2 will show the # of LP ports. TYPE 3 will show the # of HP ports. Then in the DESCRIPTION and/or FEATURES fields it will say whether or not the product is adjustable or nonadjustable, balanced or non-balanced.In the Lights category, TYPE 1 will show if the item is Halogen, Xenon, or Strobe TYPE2, & TYPE3 will always be blank because there is no further subcategorizing. See what I mean about tricky?At 10:17 PM 7/31/98, I originally asked: >1. Can I do it all with the one database?Peter says: 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. Ken says: Yes.In anser to Peter's request that I post the # of brands, the # of categories & the individual fields for each category, I'll try but the database is being buit right now. (All the client gave us was a database containing; sku, brand, title, price, and weight)There are approx. 17 different brands. Some have products in all catagories, most make products in a only a few.There are approx 11 catagories and these are the fields for each:Suits - TYPE1 full/half suit, TYPE2 wet/dry, TYPE3 sock/vest/hood, SIZE=s,m,l,xl, SIZECHART is a link to a size chart, COLOR, SEX, & TEMPRANGE are all applicable, HASIMAGE=T, IMAGE, HASLIMAGE=Sometimes, LIMAGE, DESCRIPTION is a paragraph of text, FEATURES is a list, REPLITEM1, REPLITEM2, OPPADD1 & OPPADD2 all apply to a few in this catagory Computers - TYPE1 metric/imperial, TYPE2 PC download/nitrox, TYPE3 hosesless/air-integrated, SIZE, SIZECHART, COLOR, SEX, & TEMPRANGE do not not apply, HASIMAGE=T, IMAGE, HASLIMAGE=Sometimes, LIMAGE, DESCRIPTION is a paragraph of text, FEATURES is a list, REPLITEM1, REPLITEM2, OPPADD1 & OPPADD2 all apply to a few in this catagoryLights - TYPE1 halogen/xenon/strobe, TYPE2 wattag, TYPE3 blank, SIZE is in inches, SIZECHART, COLOR, & SEX do not not apply, TEMPRANGE is used for wattage, HASIMAGE=T, IMAGE, HASLIMAGE=Never, LIMAGE, DESCRIPTION is a paragraph of text, FEATURES is a list, REPLITEM1, REPLITEM2, OPPADD1 & OPPADD2 all apply to a few in this catagoryAcceories - has 16 subcatagories that are named in the TYPE 1 field, TYPE2, & TYPE3 are blank, SIZE may be in ounces, inches, feet, or S,M,L, SIZECHART, SEX, & TEMPRANGE do not not apply, COLOR applies to some, HASIMAGE=T, IMAGE, HASLIMAGE=Sometimes, LIMAGE, DESCRIPTION is a paragraph of text, FEATURES is a list, REPLITEM1, REPLITEM2, OPPADD1 & OPPADD2 none applyDo you really want me to go through all eleven? okay.Watches - TYPE1 waterproof/water resistant, TYPE2 & TYPE3 are blank SIZE, SIZECHART, & COLOR do not not apply, but SEX does, and TEMPRANGE is used instead for depth rating, and HASIMAGE=T, IMAGE, HASLIMAGE=Sometimes, LIMAGE, DESCRIPTION is a paragraph of text, FEATURES is a list, REPLITEM1, REPLITEM2, OPPADD1 & OPPADD2 all apply to a few in this catagoryWatertight Cases - TYPE1, TYPE2 & TYPE3 are blank, SIZE is in square inches, SIZECHART, & COLOR do not not apply, but SEX does, and TEMPRANGE is used instead for depth rating, and HASIMAGE=T, IMAGE, HASLIMAGE=Never, LIMAGE, DESCRIPTION is a paragraph of text, FEATURES is a list, REPLITEM1, REPLITEM2, OPPADD1 & OPPADD2 all apply to a few in this catagoryOdds and Ends - has 12 subcatagories that are named in the TYPE 1 field, TYPE2, & TYPE3 are blank, SIZE may be in ounces, inches, feet, or S,M,L, or not applicable SIZECHART, SEX, & TEMPRANGE do not not apply, COLOR applies to some, HASIMAGE=T, IMAGE, HASLIMAGE=never, LIMAGE, DESCRIPTION is a paragraph of text, FEATURES is a list, REPLITEM1, REPLITEM2, OPPADD1 & OPPADD2 none applyPhotography - has 5 subcatagories that are named in the TYPE 1 field, TYPE2, & TYPE3 are blank, SIZE, SIZECHART, SEX, TEMPRANGE, COLOR do not not apply, HASIMAGE=T, IMAGE, HASLIMAGE=Never, LIMAGE, DESCRIPTION is a paragraph of text, FEATURES is a list, REPLITEM1, REPLITEM2, OPPADD1 & OPPADD2 some applyReels - TYPE1, TYPE2 & TYPE3 are blank, SIZE reffers to lenght of line in feet or inches, SIZECHART, COLOR, SEX, & TEMPRANGE do not not apply, and HASIMAGE=T, IMAGE, HASLIMAGE=Never, LIMAGE, DESCRIPTION is a paragraph of text, FEATURES is a list, REPLITEM1, REPLITEM2, OPPADD1 & OPPADD2 some apply Guns - has 5 subcatagories that are named in the TYPE 1 field, TYPE2, & TYPE3 are blank, SIZE reffers to shaft lenght in feet, SIZECHART, SEX, TEMPRANGE, COLOR do not not apply, HASIMAGE=T, IMAGE, HASLIMAGE=Never, LIMAGE, DESCRIPTION is a paragraph of text, FEATURES is a list, REPLITEM1, REPLITEM2, OPPADD1 & OPPADD2 some applyEducation - has 4 (books, CD-ROMS, etc.) subcatagories that are named in the TYPE 1 field, TYPE2 list the further subcatagories or subjet headers, & TYPE3 is the author, SIZE reffers to # of pages, SIZECHART, SEX, TEMPRANGE, & COLOR do not not apply, HASIMAGE=T, IMAGE, HASLIMAGE=Never, LIMAGE, DESCRIPTION is a paragraph of text, FEATURES is a list, REPLITEM1, REPLITEM2, OPPADD1 & OPPADD2 none applyWHEW!!!My next question were: >2. Do I have enough (or the right) fields to do all the different searches >I need? Peter: I don't think so. Ken: I think so.>3. Is it possible to use *that many* [showif] tags without ridiculous >slow-downs? Peter: Ken: Yes.>4. If it *would* be better to do multiple databases, say one for each >brand, how do I do a search calling up all the catagories listed in all the >databases? Peter: Ken: It is NOT better to split the db. If you do, you will be sorry later ...:( Does my somewhat brief description of the fields in each catagory make it more clear if I should split up the database?Angel J. Bennett ! We want the world and VP / Creative Dir. ! we want it... The WWW Store ! NOW! 818-905-6787 ! http://www.thewwwstore.com
Angel Bennett
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:
Multiple catalog databases and showcart (1997)
WebCat b13 CGI -shownext- (1997)
ShowNext problems (1998)
Tracking System? (1997)
WebCat2b13MacPlugIn - [include] doesn't allow creator (1997)
Performance Tuning (2006)
Using [Showif] tag. Mac (1997)
Multiple prices (1997)
WebCat for Unix?? (1997)
Snake Bites (1997)
[WebDNA] Parsing JS value to WebDNA variable or
Date Sorting (1997)
searchable list archive (1997)
Addlineitems SKU peramiter (2002)
Help! WebCat2 bug (Ben's input) (1997)
Search results problem (2003)
$Replace with [founditems] (1997)
Reversed words (1997)
logout after authenticated (2002)
Quitting WebMerchant ? (1997)