Re: Search bug. Help
This WebDNA talk-list message is from 2002
It keeps the original formatting.
numero = 43505
interpreted = N
texte = 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.>> How else are you going to tell webcat that these are >> two distinct values be it text or num. > > How about a group field search, have you tried that yet? > Or using showif's and hideif's in your founditems context? > > >> I can assume that ww, ws and wa are all for searching text. > > But as soon as you put &type=num into your search context, you are > no longer searching text. > > I had a debate with SMSI about this issue a very long time ago. > The HTML docs STILL do not make it clear that when you put a field > type parameter into your search, it forces the search to behave > differently than without it -- even though it should only be the SORT > that is done differently ... > > The docs still need to be fixed to properly reflect the manner in > which the search is messed up by the addition of a type=num > parameter in this situation. But until the docs are fixed, it's > always going to be the users who have to deal with this issue again > (and again) ... > > > >> As far as running 2 consecutive search to find 2 numeric values in the same >> field sounds a little silly. > > I don't think it's silly if it works! > > My policy when coding webdna is simple: > > If you cannot get it to work the way you first try it, don't waste > too many hours trying to force it to work the way you insist that it > should. Instead, just try a different technique -- there's usually > another technique that works -- until the bug is fixed or until you > can afford to invest the time to make it work the way you first > tried. > > You have to remember, webdna is extremely fast, and several search > contexts on a page will not phase the webdna search engine. In other > words, you won't even be able to measure (much less see) the speed > difference when searching twice vs. searching once. So if it's > EASIER to do two searches, and if it WORKS PROPERLY when doing two > searches, I see no reason why you shouldn't do it that way. > > And of course there are even more ways to skin a webcat than I > suggested and illustrated in my previous post ... > > For example, you can also use showif's and/or hideif's to remove the > ct values you don't want to include in your search results, which > leaves you with the SINGLE SEARCH that you seem to prefer: > > [search db=mydb.db&neCTdatarq=[blank]&asctsort=1&cttype=num] > [founditems] > > [showif [ct]=.20] > some stuff here ... > [/showif] > > [showif [ct]=.25] > more stuff here ... > [/showif] > > [/founditems] > [/search] > > > 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/ ------------------------------------------------------------- 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:
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.>> How else are you going to tell webcat that these are >> two distinct values be it text or num. > > How about a group field search, have you tried that yet? > Or using showif's and hideif's in your founditems context? > > >> I can assume that ww, ws and wa are all for searching text. > > But as soon as you put &type=num into your search context, you are > no longer searching text. > > I had a debate with SMSI about this issue a very long time ago. > The HTML docs STILL do not make it clear that when you put a field > type parameter into your search, it forces the search to behave > differently than without it -- even though it should only be the SORT > that is done differently ... > > The docs still need to be fixed to properly reflect the manner in > which the search is messed up by the addition of a type=num > parameter in this situation. But until the docs are fixed, it's > always going to be the users who have to deal with this issue again > (and again) ... > > > >> As far as running 2 consecutive search to find 2 numeric values in the same >> field sounds a little silly. > > I don't think it's silly if it works! > > My policy when coding webdna is simple: > > If you cannot get it to work the way you first try it, don't waste > too many hours trying to force it to work the way you insist that it > should. Instead, just try a different technique -- there's usually > another technique that works -- until the bug is fixed or until you > can afford to invest the time to make it work the way you first > tried. > > You have to remember, webdna is extremely fast, and several search > contexts on a page will not phase the webdna search engine. In other > words, you won't even be able to measure (much less see) the speed > difference when searching twice vs. searching once. So if it's > EASIER to do two searches, and if it WORKS PROPERLY when doing two > searches, I see no reason why you shouldn't do it that way. > > And of course there are even more ways to skin a webcat than I > suggested and illustrated in my previous post ... > > For example, you can also use showif's and/or hideif's to remove the > ct values you don't want to include in your search results, which > leaves you with the SINGLE SEARCH that you seem to prefer: > > [search db=mydb.db&neCTdatarq=[blank]&asctsort=1&cttype=num] > [founditems] > > [showif [ct]=.20] > some stuff here ... > [/showif] > > [showif [ct]=.25] > more stuff here ... > [/showif] > > [/founditems] > [/search] > > > 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/ ------------------------------------------------------------- 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/
marc malacarme
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:
WC2.0 Memory Requirements (1997)
Cobalt and WebCatalog, do they work together? (2000)
Do triggers work on Macs? (2000)
WebCat2 several catalogs? (1997)
Problems adding stuff to the shopping cart. (1997)
Searching multiple Databases (1997)
server2003 (2004)
WebCat2b12 - nesting [tags] (1997)
UPDATEDONE question ... (1998)
Problems with [Applescript] (1997)
Cookies (1999)
how is this possible (2000)
New WebDNA Example from Olin -- (1998)
username = 115 (1999)
WebCat2 - Getting to the browser's username/password data (1997)
[protect admin] (1997)
[WebDNA] Anyone using Ubuntu 17.04 yet? (2017)
notification solutions (1997)
When do we get to request new features? (1999)
listcookies works only sometimes (1997)