Re: Search bug. Help
This WebDNA talk-list message is from 2002
It keeps the original formatting.
numero = 43503
interpreted = N
texte = >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/
Associated Messages, from the most recent to the oldest:
>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/
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:
Authorize.Net (2003)
If search results are blank... (2003)
Total found of each unique field (2003)
credit card (1997)
Generating Report Totals (1997)
Anyone have an invoicing system? (1999)
Can he do that? (1998)
PCS Frames (1997)
all records returned. (1997)
[WebDNA] PROBLEM WITH [SQL] (2009)
Ghostly cached webpage (2000)
[WebDNA] OT: 2 php/MySQL & 1 Flash person needed FT (2008)
WebCatalog for Postcards ? (1997)
webcat nt (1997)
referrer usage (1997)
Re:2nd WebCatalog2 Feature Request (1996)
SOP for WebDNA talk - MSNBot Crashing (2004)
Bug Report, maybe (1997)
SendMail - Idea (2000)
Introduction/Tutorial/QuickStart (1997)