Re: <fieldname>summ=T
This WebDNA talk-list message is from 2003
It keeps the original formatting.
numero = 54828
interpreted = N
texte = Alright, your search is all messed up, or your database, or both! First of all if you "ne" (!=) the [ProdID] in your search then you return nothing because your database lists all CATEGORY=shoes + BRAND=Z with the same PRODUCT_ID eliminating them all!!! Second, If you SUMM on PRODUCT_ID (which are all the same in your db) you only get 1 product listed because they all have the same PRODUCT_ID!!!! Have you even read your own code here? What is this a test? The Fix: 1.) Delete: &nePRODUCT_IDdatarq=[ProdID] 2.) Delete: &PRODUCT_IDsumm=T 3.) Add: &IDsumm=T Hope this helps! On Wednesday, December 10, 2003, at 09:57 AM, Marc Kaiwi wrote: > I'll copy the code from your test page there and take it to back to my > shop and try it out here (if you don't mind me doing so?). <--- > That's what the Grinch told little Cindy Who about her christmas tree! > : c) Hahahaha!!! > > Is that page still there. > > It's got to be something simple. > > On Wednesday, December 10, 2003, at 09:31 AM, Donovan Brooke wrote: > >> Marc Kaiwi wrote: >> >>> It's too confusing with all that extra stuff you have going on all >>> over the place ... >>> break it down to include only the problem areas, hard code the >>> search and lookups and I'm sure you'll find the problem. >>> Good Luck, >>> MK >> >> Hmm well thanks. I don't need the NO_INVENTORY in there for testing >> but >> the rest I *do* need for this test so I don't think I need to change >> anything. >> >> I know (kindof) what the issue is, I just can't wrap my head around >> the fix >> right now. >> >> I am including: >> &eqCATEGORYdata=[theCATEGORY]&eqBRANDdata=[theBRAND] >> >> to try and narrow the best matches... so if the customer >> is looking at a X brand Shoe, the results ideally would >> find another type of X brand shoe. However, I don't want >> it to be necessary in the search.. thus the missing "rq's". >> >> However, what I'm finding is that because they are not necessary, >> the search is finding totally unrelated products based on the >> other perams (like its supposed to). I just can't figure out >> how to narrow the perams to not find totally unrelated products. >> >> something like, if both category *and* brand do not match the >> respective >> brand and category values, then don't display.?? >> >> I am thinking that if my perams would narrow better, then I could use >> the >> summ=T on the product_ID field to only bring up one base type of >> product. >> >> Any ideas? >> >> thanks, >> Donovan > > Signed: Marc Kaiwi > > > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list
. > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to > > Web Archive of this list is at: http://webdna.smithmicro.com/ > > Signed: Marc Kaiwi ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Alright, your search is all messed up, or your database, or both! First of all if you "ne" (!=) the [ProdID] in your search then you return nothing because your database lists all CATEGORY=shoes + BRAND=Z with the same PRODUCT_ID eliminating them all!!! Second, If you SUMM on PRODUCT_ID (which are all the same in your db) you only get 1 product listed because they all have the same PRODUCT_ID!!!! Have you even read your own code here? What is this a test? The Fix: 1.) Delete: &nePRODUCT_IDdatarq=[ProdID] 2.) Delete: &PRODUCT_IDsumm=T 3.) Add: &IDsumm=T Hope this helps! On Wednesday, December 10, 2003, at 09:57 AM, Marc Kaiwi wrote: > I'll copy the code from your test page there and take it to back to my > shop and try it out here (if you don't mind me doing so?). <--- > That's what the Grinch told little Cindy Who about her christmas tree! > : c) Hahahaha!!! > > Is that page still there. > > It's got to be something simple. > > On Wednesday, December 10, 2003, at 09:31 AM, Donovan Brooke wrote: > >> Marc Kaiwi wrote: >> >>> It's too confusing with all that extra stuff you have going on all >>> over the place ... >>> break it down to include only the problem areas, hard code the >>> search and lookups and I'm sure you'll find the problem. >>> Good Luck, >>> MK >> >> Hmm well thanks. I don't need the NO_INVENTORY in there for testing >> but >> the rest I *do* need for this test so I don't think I need to change >> anything. >> >> I know (kindof) what the issue is, I just can't wrap my head around >> the fix >> right now. >> >> I am including: >> &eqCATEGORYdata=[theCATEGORY]&eqBRANDdata=[theBRAND] >> >> to try and narrow the best matches... so if the customer >> is looking at a X brand Shoe, the results ideally would >> find another type of X brand shoe. However, I don't want >> it to be necessary in the search.. thus the missing "rq's". >> >> However, what I'm finding is that because they are not necessary, >> the search is finding totally unrelated products based on the >> other perams (like its supposed to). I just can't figure out >> how to narrow the perams to not find totally unrelated products. >> >> something like, if both category *and* brand do not match the >> respective >> brand and category values, then don't display.?? >> >> I am thinking that if my perams would narrow better, then I could use >> the >> summ=T on the product_ID field to only bring up one base type of >> product. >> >> Any ideas? >> >> thanks, >> Donovan > > Signed: Marc Kaiwi > > > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to > > Web Archive of this list is at: http://webdna.smithmicro.com/ > > Signed: Marc Kaiwi ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Marc Kaiwi
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:
WebCatalog2 Feature Feedback (1996)
WebCatalog on Linux (2000)
random images (1997)
CommandSecurity? (1997)
search form problem.. (1997)
WebCat2: Found Items syntax, etc. (1997)
WebCat editing, SiteGuard & SiteEdit (1997)
[WebDNA] [BULK] Mac OS X LION has no FastCGI (2011)
Web Catalog 2 demo (1997)
GoodPath and MoveFile (2000)
Price Not Appearing (2000)
ShowNext (1997)
wish list (2002)
Max Record length (1997)
Bug (feature) in v6 listfiles shows hidden files ... (2004)
4.5 Upgrade (2003)
What really killed WebDNA? (2007)
Late on Friday.... brain fried (2002)
BBEdit and WebCatalog 2.0? (1997)
Using Cookie for client specific info? (1997)