Re: searching multiple databases
This WebDNA talk-list message is from 1997
numero = 14795
interpreted = N
texte = >Mabye i'm not understanding this correctly. > >I'm attempting to search another database using the [search] command in my >template based on the sku of a product selected on a previous page. If a >customer clicks on Shirt, I need to show on Detail.tmpl color options, I >had thought that building a colors.db and haveing fields sku and color, >hoping to search that db by that perticular sku selected and returning a >
menu with the perticular colors available to that item. > >I tried >[search db=colors.db&geSKUdata=[sku]] >[founditems][Color][/founditems]Okay, here are 3 things you need to correct:1- There's no [/search] after your founditems context. 2- If you're searching for a matching sku, you have to use eqSKUdata=[sku], not geSKUdata=[sku]. 3- Simply putting [color] inside your founditems context will only make a list, it won't create a popup menu. Youy have to put your values inside the founditems context and the tags outside the founditems context in order to create a popup menu. I'm not sure how you're going to generate a unique SKU value when you have only a single record in your products database. You can create unique SKU values by combining [cart]-generated SKU's with other special codes for colors and sizes, is that what you're doing?The way I usually create products databases, every unique item has its own record. This makes it easier to administer in the long run. If you sell ONE style of shirt in 5 different colors and 3 different sizes, you should have 15 different records in your database -- one for each combination of those 5 colors and 3 sizes.Then when someone does a search for that particular style of shirt (before he/she knows which color or size to choose from), your search should be a 'summary' search for the shirt style. A summary search for that style of shirt will retrieve only ONE of the 15 records in the database.When your visitor gets the results of this search, it will show a single style, and on that page you can then give your visitors the choice of 5 colors and 3 sizes. When they make their color and size selections, a new search can be performed that retrieves the exact match record from the 15 possible matching records in your database.If you don't want to bother doing it that way, then you can put a single record in your databases for the shirt's style, then store your color and size data in another database or two. But then you will have to create SKU values on the fly ... not easy, but it works, and it keeps your main products database smaller, althiugh in most cases, that's not really an issue. Sincerely, Ken Grome WebDNA Solutions http://www.smithmicro.com/webdnasolutions/.
Associated Messages, from the most recent to the oldest:[search] command in my >template based on the sku of a product selected on a previous page. If a >customer clicks on Shirt, I need to show on Detail.tmpl color options, I >had thought that building a colors.db and haveing fields sku and color, >hoping to search that db by that perticular sku selected and returning a > menu with the perticular colors available to that item. > >I tried >[search db=colors.db&geSKUdata=[sku]] >[founditems] [Color][/founditems]Okay, here are 3 things you need to correct:1- There's no [/search] after your founditems context. 2- If you're searching for a matching sku, you have to use eqSKUdata=[sku], not geSKUdata=[sku]. 3- Simply putting [color] inside your founditems context will only make a list, it won't create a popup menu. Youy have to put your values inside the founditems context and the tags outside the founditems context in order to create a popup menu. I'm not sure how you're going to generate a unique SKU value when you have only a single record in your products database. You can create unique SKU values by combining [cart] -generated SKU's with other special codes for colors and sizes, is that what you're doing?The way I usually create products databases, every unique item has its own record. This makes it easier to administer in the long run. If you sell ONE style of shirt in 5 different colors and 3 different sizes, you should have 15 different records in your database -- one for each combination of those 5 colors and 3 sizes.Then when someone does a search for that particular style of shirt (before he/she knows which color or size to choose from), your search should be a 'summary' search for the shirt style. A summary search for that style of shirt will retrieve only ONE of the 15 records in the database.When your visitor gets the results of this search, it will show a single style, and on that page you can then give your visitors the choice of 5 colors and 3 sizes. When they make their color and size selections, a new search can be performed that retrieves the exact match record from the 15 possible matching records in your database.If you don't want to bother doing it that way, then you can put a single record in your databases for the shirt's style, then store your color and size data in another database or two. But then you will have to create SKU values on the fly ... not easy, but it works, and it keeps your main products database smaller, althiugh in most cases, that's not really an issue. Sincerely, Ken Grome WebDNA Solutions http://www.smithmicro.com/webdnasolutions/.
Kenneth Grome
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:
Javascripts (1998) space at start of menu (2000) Don'y know if this is a sily question... (2003) WebCatalog2 Feature Feedback (1996) Re:no [search] with NT (1997) suffix mapping, use of cache, etc. (1997) getting images' width/height (1998) WebCat2: multiple currency support (1997) Download URL & access on the fly ? (1997) Live server problems (1999) IIS4b2 and WebCatalog b19 (1997) WCS Newbie question (1997) WebCatalog for guestbook ? (1997) Unexpected error (1997) [WebDNA] WebDNA 7 (2011) rounding onlu UP (2002) Multiple Replaces? (1997) Close-to Comparison Code (1998) Need relative path explanation (1997) WCS Newbie question (1997)