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:
AccountAuthorizer doesn't seem to work (1997)
Version 2.1.3 changes ... (1998)
E-Mailer (WebCatb15acgiMac) (1997)
[browsername] not working? (1997)
Unexceling (was I need a smart quote...) (1999)
Fun with dates (1997)
Erotic Sites (1997)
date search not working when type=date specified (2007)
'does not contain' operator needed ... (1997)
international time (1997)
Is there a max number of fields? (1998)
No luck with taxes (1997)
variables in [addlineitem] (1998)
all records returned. (1997)
[ModDate] & [ModTime] ? (1997)
Looking for 5 to 12 shops with 3 URLs & statements (1997)
Emailer problems. (1998)
Pager notification of completed orders (1998)
Error 11 (1996)
Can this be done? (2003)