Re: select menus & database design
This WebDNA talk-list message is from 1998
numero = 17807
interpreted = N
texte = Kenneth Grome wrote: > >>What we'd like is for our search results template to recognize when a > >>product has size and color options, and to generate a
menu > >>which shows the appropriate options. > >> > >>What would be a good database/template design to create such a feature? > > Another way to go is simply to add a few extra fields, one for color, one for size, etc., so you can search on those fields individually instead of trying to select the equivalent values from portions of the SKU. This solution is easier to deal with as far as WebDNA coding is concerned because it's always easier to search on a different field than to search on a portion of the same field. So if your database isn't all that big anyways, I would do it this easy way, but if you're concerned about the size of your database then I would use the first suggestion. >Okay, got it.First I generated popups just for color, with a . That worked great. Adding to cart worked fine. Then we realized we need to provide multiple size options as well. So then we're offering two popup options -- obviously we can't call both form elements sku. I'd hoped I could just offer the add command our product's title, size, and color, and it could pull the sku from the database... but no dice.Should I collapse the size and color fields in the database? I can't think of any other solutions...Thanks, -- John Masterson masterson@montana.com webmaster@everyweek.com Assistant Webmaster, Pollmaster Webmaster Internet Connect Services Missoula Independent http://www.montana.com/ics/ http://www.everyweek.com
Associated Messages, from the most recent to the oldest: menu > >>which shows the appropriate options. > >> > >>What would be a good database/template design to create such a feature? > > Another way to go is simply to add a few extra fields, one for color, one for size, etc., so you can search on those fields individually instead of trying to select the equivalent values from portions of the SKU. This solution is easier to deal with as far as WebDNA coding is concerned because it's always easier to search on a different field than to search on a portion of the same field. So if your database isn't all that big anyways, I would do it this easy way, but if you're concerned about the size of your database then I would use the first suggestion. >Okay, got it.First I generated popups just for color, with a . That worked great. Adding to cart worked fine. Then we realized we need to provide multiple size options as well. So then we're offering two popup options -- obviously we can't call both form elements sku. I'd hoped I could just offer the add command our product's title, size, and color, and it could pull the sku from the database... but no dice.Should I collapse the size and color fields in the database? I can't think of any other solutions...Thanks, -- John Masterson masterson@montana.com webmaster@everyweek.com Assistant Webmaster, Pollmaster Webmaster Internet Connect Services Missoula Independent http://www.montana.com/ics/ http://www.everyweek.com
J. Masterson
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:
emailer (1997) Emailer setup (1997) How flexible is Shipping? (1997) Looking For WebCatalog Migration Assistance (2003) Checking two required fields (1998) RAM variables (1997) Weird happenings (1998) Next (1997) DNABill Screen Shots (2003) [WebDNA] Error. WebDNA (version 5.1g or later) is not running. (2012) [ConvertChars] problem (1997) Not really WebCat (1997) Exclamation point (1997) [WebDNA] Friday February 13, 2009 (2009) 2.0Beta Command Ref (can't find this instruction) (1997) WebCat2b13 Mac plugin - [sendmail] and checkboxes (1997) [WebDNA] Donation... reading the header /url (2017) [SHOWIF AND/OR] (1997) Malformed Pages (1999) new cart IDs being assigned somehow (1997)