Re: Some Advise needed
This WebDNA talk-list message is from 1997
It keeps the original formatting.
numero = 12488
interpreted = N
texte = >>For example you have a bottle of gear lube that comes in 4 oz., 8 oz. and>>12 oz. sizes, with prices of $4.00, $7.00 and $10.00.>>The simplest approach (but maybe not the prettiest) is to pretend like all >those variations are different products in your database. So when people >search for lube, they see 3 different SKUs, 3 different prices, and 3 >different descriptions.>>But if you truly want to make them look like 'variations' of a single >product, you can do some more work like the following:I have been working on a similar type project. Grant I tried your suggestion of the embedded db's which works fine, but I found that the data magagment was a little messy.I've used a single database but have something like this:SKU SubType Description Price GroupingLube4 1 4 oz. 4.00 LUBELube8 2 8 oz. 7.00 LUBELube12 3 12 oz. 10.00 LUBEWaxV 1 Vanilla 9.00 WAXWaxC 2 Cinnamon 9.00 WAXI requies the convincing the client about the format, but it works fine.For searching I did normal search, for all the products, but added an extra search which summarises all the products.So you would get in your results. LUBE WAXas items to select,When you select the detail, it list the items, plus all the variations, as per the DB.If you want to look at a test DB I'm working on you can check out:http://www.conexus.com.au/webcatalog/conexusnew/entry.tmplThis is very rough at the momment, but shows the concept I'm talking about. If you need some helper code, let me know.cheers,Rick---------------------------------------------------------------------------Key Options Pty. Ltd.P.O. Box 1150Castle Hill, NSW, 2154AustraliaTel:+61-2-9899-9564Fax:+61-2-9899-9318Mob: 0412-205-113-----BEGIN PGP PUBLIC KEY BLOCK-----mQBPAzNMLcoAAAECAL5yuN2krMXeMwfcZPvWFJ0d6oMd++Pafsx0MkIGoTmHLz9iLYHOiyZfeWNcLRd4c6xHlPN36lyPe9Uw9jwbaQEAEQEAAbQiUmljaGFyZCBXeWxpZSA8cmlja3dAbWFnbmEuY29tLmF1PokAVQMFEDNLoSp71TD2PBtpAQEB3kMCAKQ5zd+aPODE2zw2Rht1duf4kVV6yXdC+ZSGYT0uGmkidgHS/Jw+uJvzHnKvR2ziAFrVpYMY6WMaf06yWFvekvc==prwK-----END PGP PUBLIC KEY BLOCK-----
Associated Messages, from the most recent to the oldest:
>>For example you have a bottle of gear lube that comes in 4 oz., 8 oz. and>>12 oz. sizes, with prices of $4.00, $7.00 and $10.00.>>The simplest approach (but maybe not the prettiest) is to pretend like all >those variations are different products in your database. So when people >search for lube, they see 3 different SKUs, 3 different prices, and 3 >different descriptions.>>But if you truly want to make them look like 'variations' of a single >product, you can do some more work like the following:I have been working on a similar type project. Grant I tried your suggestion of the embedded db's which works fine, but I found that the data magagment was a little messy.I've used a single database but have something like this:SKU SubType Description Price GroupingLube4 1 4 oz. 4.00 LUBELube8 2 8 oz. 7.00 LUBELube12 3 12 oz. 10.00 LUBEWaxV 1 Vanilla 9.00 WAXWaxC 2 Cinnamon 9.00 WAXI requies the convincing the client about the format, but it works fine.For searching I did normal search, for all the products, but added an extra search which summarises all the products.So you would get in your results. LUBE WAXas items to select,When you select the detail, it list the items, plus all the variations, as per the DB.If you want to look at a test DB I'm working on you can check out:http://www.conexus.com.au/webcatalog/conexusnew/entry.tmplThis is very rough at the momment, but shows the concept I'm talking about. If you need some helper code, let me know.cheers,Rick---------------------------------------------------------------------------Key Options Pty. Ltd.P.O. Box 1150Castle Hill, NSW, 2154AustraliaTel:+61-2-9899-9564Fax:+61-2-9899-9318Mob: 0412-205-113-----BEGIN PGP PUBLIC KEY BLOCK-----mQBPAzNMLcoAAAECAL5yuN2krMXeMwfcZPvWFJ0d6oMd++Pafsx0MkIGoTmHLz9iLYHOiyZfeWNcLRd4c6xHlPN36lyPe9Uw9jwbaQEAEQEAAbQiUmljaGFyZCBXeWxpZSA8cmlja3dAbWFnbmEuY29tLmF1PokAVQMFEDNLoSp71TD2PBtpAQEB3kMCAKQ5zd+aPODE2zw2Rht1duf4kVV6yXdC+ZSGYT0uGmkidgHS/Jw+uJvzHnKvR2ziAFrVpYMY6WMaf06yWFvekvc==prwK-----END PGP PUBLIC KEY BLOCK-----
Richard Wylie
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:
WebCat2b13MacPlugIn - [include] (1997)
WebCat2 - [SendNews] (1997)
Here we go again...WebDNA - SQL- Clustering (2006)
WC2.0 Memory Requirements (1997)
Duplicates (1998)
Another bug to squash (WebCat2b13 Mac .acgi) (1997)
Grouping fields problem (1998)
stuck time (1998)
question: Eudora 3.1.1 (1997)
Spaces in FormVariables (2001)
shipcost (1997)
still having shipCost.db Problem (1997)
sorting and summarizing (1998)
Templates for Customer Database? (1997)
Help! WebCat2 bug (1997)
Showif -what am I missing??? (1999)
Questions! (2000)
Doing VALIDCARD right? (1998)
[OT] Am I an Idiot? (2004)
DHTML or Java Programmers (2000)