Re: Search bug. Help
This WebDNA talk-list message is from 2002
It keeps the original formatting.
numero = 43495
interpreted = N
texte = Okay, first of all, you do NOT need the &CTtype=num unless you're going to sort the results, or unless you're going to actually perform a search that does some kind of greater than or less than comparison instead of an equal to or a contains comparison.But you're not sorting the results, nor are you trying to do a range-based search, so you should definitely leave the &CTtype=num out of the search.And if all you're looking for is a way to retrieve the records with (shape=rd) AND (ct=.20 or ct=.25) you can easily run two consecutive searches that perform EQUAL TO comparisons for the exact records you need:[search db=mydb.db&eqSHAPEdatarq=rd&eqCTdatarq=.20] [founditems] [/founditems] [/search][search db=mydb.db&eqSHAPEdatarq=rd&eqCTdatarq=.25] [founditems] [/founditems] [/search]Or if you do not have any other values in the ct field within the range of .20-.25 you could easily perform a RANGE search:[search db=mydb.db&eqSHAPEdatarq=rd&rnCTdatarq=.20 .25&CTtype=num]Or you could do a search that finds all the values which are CLOSE TO the designated value in the first cl parameter:[search db=mydb.db&eqSHAPEdatarq=rd&clCTdatarq=.225&clCTdatarq=.025&CTtype=num]Or if you're actually seeking all the rd records which are less than 0.51 (for example) you could do this search:[search db=mydb.db&eqSHAPEdatarq=rd&lsCTdatarq=0.51&CTtype=num]In other words, there's usually lots of ways to do things in webdna ... :)>The following search returned mime header information to the browser and >then crashes webcat. > >[search db=mydb.db&eqSHAPEdatarq=rd&woCTdatarq=.20,.25,&CTtype=num] > >Mydb looks like this: > >shape ct >rd .20 >rd .25 >pr .50 >rd 1.25 >rd 1.20 > >When I add cttype=num it crashes but without it it finds .20 inside 1.20 > >IF I remove the , it doesn't crash but only finds the first value .20 and >not .20 and .25. > >How do you tell webcat to search for multiple values ie: .20 & .25 as whole >numbers. Shouldn't there be a wn like there is a ww in wordbreaks. > >Any help would be appreciated > > > >------------------------------------------------------------- >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://search.smithmicro.com/ ------------------------------------------------------------- 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://search.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Okay, first of all, you do NOT need the &CTtype=num unless you're going to sort the results, or unless you're going to actually perform a search that does some kind of greater than or less than comparison instead of an equal to or a contains comparison.But you're not sorting the results, nor are you trying to do a range-based search, so you should definitely leave the &CTtype=num out of the search.And if all you're looking for is a way to retrieve the records with (shape=rd) AND (ct=.20 or ct=.25) you can easily run two consecutive searches that perform EQUAL TO comparisons for the exact records you need:[search db=mydb.db&eqSHAPEdatarq=rd&eqCTdatarq=.20] [founditems] [/founditems] [/search][search db=mydb.db&eqSHAPEdatarq=rd&eqCTdatarq=.25] [founditems] [/founditems] [/search]Or if you do not have any other values in the ct field within the range of .20-.25 you could easily perform a RANGE search:[search db=mydb.db&eqSHAPEdatarq=rd&rnCTdatarq=.20 .25&CTtype=num]Or you could do a search that finds all the values which are CLOSE TO the designated value in the first cl parameter:[search db=mydb.db&eqSHAPEdatarq=rd&clCTdatarq=.225&clCTdatarq=.025&CTtype=num]Or if you're actually seeking all the rd records which are less than 0.51 (for example) you could do this search:[search db=mydb.db&eqSHAPEdatarq=rd&lsCTdatarq=0.51&CTtype=num]In other words, there's usually lots of ways to do things in webdna ... :)>The following search returned mime header information to the browser and >then crashes webcat. > >[search db=mydb.db&eqSHAPEdatarq=rd&woCTdatarq=.20,.25,&CTtype=num] > >Mydb looks like this: > >shape ct >rd .20 >rd .25 >pr .50 >rd 1.25 >rd 1.20 > >When I add cttype=num it crashes but without it it finds .20 inside 1.20 > >IF I remove the , it doesn't crash but only finds the first value .20 and >not .20 and .25. > >How do you tell webcat to search for multiple values ie: .20 & .25 as whole >numbers. Shouldn't there be a wn like there is a ww in wordbreaks. > >Any help would be appreciated > > > >------------------------------------------------------------- >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://search.smithmicro.com/ ------------------------------------------------------------- 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://search.smithmicro.com/
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:
Re:Emailer and encryption (1997)
email preferences on NT (1997)
WebCatalog 2.0 & WebDNA docs in HTML ... (1997)
Browser Check for WebDNA compatability (1999)
MIMEHeaders (2004)
[OT] Airport Problem (2003)
This list needs a digest: rant, rave... (1997)
Setting up WebCatalog with Retail Pro data (1996)
[showif] with ! (2000)
Getting total number of items ordered (1997)
[WebDNA] USPS interface (2008)
Spell Check (2003)
searching with if/then (2004)
Why are some admin pages not encrypted? (2000)
2.0Beta Command Ref (can't find this instruction) (1997)
WebCommerce Security Alert! (1996)
Friday night shopping site joke (1997)
One more time (1997)
New public beta available (1997)
Date problems (1997)