Re: Search bug. Help
This WebDNA talk-list message is from 2002
It keeps the original formatting.
numero = 43551
interpreted = N
texte = >Marc, > >What if your CT field contained NO decimals? You could multiply all your >carat sizes by 100 before they go into the database. Then, divide by 100 and >wrap the result in a [format] tag to get the 2 decimal places in the >[founditems] loop. > >This might help with the sorting issues. > >[search >db=loose-dia.db&eqSHAPEdatarq=rd&woCTdatarq=20,25&CTword=ww&CTwbrk=,&CTtype= >num&woCOLORdatarq=a,b,c&woCLARITYdatarq=vvs1,vvs2&asCOLORsort=1&asCLARITYsor >t=2&asCTsort=3&startat=[startat]&max=[themax]] No, I don't think this is going to help ...It's not the decimal point that's causing the problem, it's the inconsistency between the search and the sort parameters on the CT field that's causing the problem ...Marc is trying to SEARCH on the CT field as if it is a text field. But at the same time he is also trying to SORT on the CT field as if it is a numeric field:This is a text-based comparison: &woCTdatarq=20,25This defines the field as numeric (not only for sorting purposes, but also for searching purposes: &CTtype=num5... and you cannot use both of these parameters at the same time on the same field without getting the wrong results -- depending upon the actual values stored in the CT field, of course.That's why I suggested that he 'normalize' the format of his numeric values in the CT field. If he does this, then the CT field can be searched WITHOUT the &CTtype=num parameter. This would cause both the search and the sort to be performed as 'text' values, thus eliminating the 'inconsistency' that's been causing his problems.A properly configured search string that does the searching and sorting on two separate fields (by using the group field technique) would probably also fix this problem ... > > >[search >db=loose-dia.db&eqSHAPEdatarq=rd&woCTdatarq=20,25&CTword=ww&CTwbrk=,&CTtype= >num&woCOLORdatarq=a,b,c&woCLARITYdatarq=vvs1,vvs2&asCOLORsort=1&asCLARITYsor >t=2&asCTsort=3&startat=[startat]&max=[themax]] > > > >On 9/17/02 11:20 PM, marc malacarme
wrote: > >> First I'd like to thank you for tacking the time to help. >> >> The reason I can't do multiple searches is because the results has about 100 >> results per search and the sorting is critical. >> >> Here is the full search: >> [search db=loose-dia.db&eqshapedatarq=rd&woCTdatarq=.20, >> .25&CTword=ww&CTwbrk=,&CTtype=num&wocolordatarq=a,b,c&woclaritydatarq=vvs1,v >> vs2&colorsort=1&colorsdir=as&claritysort=2&claritysdir=as&ctsort=3&ctsddir=a >> s&startat=[startat]&max=[themax]] >> >> You see that ct is the last to be sorted. I thought about nesting searches >> but it is not feasible because the of the amount of searches it would have >> to perform. This is my main search page meaning that many users will be >> accessing the page simultaneously and 100 searches per request would be too >> much for my server. Not to mention that the page is already littered with >> lookups and 3 other searches on other databases. >> >> I can't do a range search because I want users to be able to omit certain >> values that might fit in the range. The way the user decides what values to >> search Ct with is with check boxes in the form .25 .33 .50 .60 .50 .75 .100. >> They can select any combination not necessarily in order. > > >--------------------------------------------------------------------- >Clint Davis >Webmaster / Interactive Media Specialist >Gray Loon Marketing Group, Inc. http://www.grayloon.com >204 Main Street | Evansville, IN 47708 | Phone:812-422-9999 >--------------------------------------------------------------------- > > >------------------------------------------------------------- >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/Sincerely, Kenneth Grome--------------------------------------------------- WebDNA Professional Training and Development Center 175 J. Llorente Street +63 (32) 255-6921 Cebu City, Cebu 6000 kengrome@webdna.net Philippines http://www.webdna.net ---------------------------------------------------------------------------------------------------------------- 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:
>Marc, > >What if your CT field contained NO decimals? You could multiply all your >carat sizes by 100 before they go into the database. Then, divide by 100 and >wrap the result in a [format] tag to get the 2 decimal places in the >[founditems] loop. > >This might help with the sorting issues. > >[search >db=loose-dia.db&eqSHAPEdatarq=rd&woCTdatarq=20,25&CTword=ww&CTwbrk=,&CTtype= >num&woCOLORdatarq=a,b,c&woCLARITYdatarq=vvs1,vvs2&asCOLORsort=1&asCLARITYsor >t=2&asCTsort=3&startat=[startat]&max=[themax]] No, I don't think this is going to help ...It's not the decimal point that's causing the problem, it's the inconsistency between the search and the sort parameters on the CT field that's causing the problem ...Marc is trying to SEARCH on the CT field as if it is a text field. But at the same time he is also trying to SORT on the CT field as if it is a numeric field:This is a text-based comparison: &woCTdatarq=20,25This defines the field as numeric (not only for sorting purposes, but also for searching purposes: &CTtype=num5... and you cannot use both of these parameters at the same time on the same field without getting the wrong results -- depending upon the actual values stored in the CT field, of course.That's why I suggested that he 'normalize' the format of his numeric values in the CT field. If he does this, then the CT field can be searched WITHOUT the &CTtype=num parameter. This would cause both the search and the sort to be performed as 'text' values, thus eliminating the 'inconsistency' that's been causing his problems.A properly configured search string that does the searching and sorting on two separate fields (by using the group field technique) would probably also fix this problem ... > > >[search >db=loose-dia.db&eqSHAPEdatarq=rd&woCTdatarq=20,25&CTword=ww&CTwbrk=,&CTtype= >num&woCOLORdatarq=a,b,c&woCLARITYdatarq=vvs1,vvs2&asCOLORsort=1&asCLARITYsor >t=2&asCTsort=3&startat=[startat]&max=[themax]] > > > >On 9/17/02 11:20 PM, marc malacarme wrote: > >> First I'd like to thank you for tacking the time to help. >> >> The reason I can't do multiple searches is because the results has about 100 >> results per search and the sorting is critical. >> >> Here is the full search: >> [search db=loose-dia.db&eqshapedatarq=rd&woCTdatarq=.20, >> .25&CTword=ww&CTwbrk=,&CTtype=num&wocolordatarq=a,b,c&woclaritydatarq=vvs1,v >> vs2&colorsort=1&colorsdir=as&claritysort=2&claritysdir=as&ctsort=3&ctsddir=a >> s&startat=[startat]&max=[themax]] >> >> You see that ct is the last to be sorted. I thought about nesting searches >> but it is not feasible because the of the amount of searches it would have >> to perform. This is my main search page meaning that many users will be >> accessing the page simultaneously and 100 searches per request would be too >> much for my server. Not to mention that the page is already littered with >> lookups and 3 other searches on other databases. >> >> I can't do a range search because I want users to be able to omit certain >> values that might fit in the range. The way the user decides what values to >> search Ct with is with check boxes in the form .25 .33 .50 .60 .50 .75 .100. >> They can select any combination not necessarily in order. > > >--------------------------------------------------------------------- >Clint Davis >Webmaster / Interactive Media Specialist >Gray Loon Marketing Group, Inc. http://www.grayloon.com >204 Main Street | Evansville, IN 47708 | Phone:812-422-9999 >--------------------------------------------------------------------- > > >------------------------------------------------------------- >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/Sincerely, Kenneth Grome--------------------------------------------------- WebDNA Professional Training and Development Center 175 J. Llorente Street +63 (32) 255-6921 Cebu City, Cebu 6000 kengrome@webdna.net Philippines http://www.webdna.net ---------------------------------------------------------------------------------------------------------------- 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:
WebCat2 - Getting to the browser's username/password data (1997)
$append (1998)
Suffix Mapping (1997)
Where is the linux 4.02b5 FTP download located? (2000)
WCS Newbie question (1997)
WebCatalog for guestbook ? (1997)
BadSuffix with 2.1b3 cgi (1997)
taxTotal (1997)
Speaking of... (1999)
Transferring textareas (1997)
Problem 2 of 2 (was: Shipping Confusion) (2000)
WebCatalog for guestbook ? (1997)
Server Load Tester (2000)
Grant, please help me ... (1997)
Summing fields (1997)
[addlineitems] (1997)
WebCat & WebTen (1997)
[addlineitems] display (1997)
Thanks ! (1997)
[Announce] Newest Commerce Site based on WebCatalog (1997)