Re: searching illegal HTML
This WebDNA talk-list message is from 2002
It keeps the original formatting.
numero = 44425
interpreted = N
texte = see below...At 4:09 PM 10/25/02, Michael Davis wrote: >On Friday, October 25, 2002, at 12:23 PM, lb Lawrence wrote: > >>Hi, >> >>I have been going round and round with this problem. >> >>I have to search a db that have illegal HTML in the fields to search >> >>like bébé Thaïlande athléte >> >>I have tried >> >>[search db=admin/image.db[!] >>[/!]&group1field=KEY[!] >>[/!]&waGroup1datarq=[UnURL][field1][/UnURL][!] >>[/!]&group2field=KEY[!] >>[/!]&wnGroup2datarq=[UnURL][field2][/UnURL][!] >>[/!]&group3field=Orient[!] >>[/!]&woGroup3datarq=[Orient][!] >>[/!]&startat=[startat][!] >>[/!]&MAX=[MAX][!] >>[/!]&asDOSSIER_EDITEURsort=1[!] >>[/!]&asSKUsort=2] >> >>I thought [UnURL] would fix my problem but nothing is working >> > >Do not use [unurl]. > >Problems with your search that I see... You are using grouping >without actually grouping any fields. You are also comparing the >same field more than once in the same search. The first problem may >work just fine, but is not necessary. The second problem will >absolutely break your search context. You cannot do two comparisons >on the KEY field like that. If you are saying KEY word-and = >field1, then use a [hideif [url][KEY][/url]=[url][field2][/url]] >within the [founditems] instead of the second KEY word-not field >comparison. > >Mike >Actually the method above does work in general and is specifically designed to allow you to search the same field two times.While you cannot say waKEYdatarq=XX YY ZZ&wnKEYdatarq=YY, as these both search a key field term named KEY, you can assign the field KEY to two different groups then search each group, thus effectively searching the same field twice.So, searching group1field=KEY&waGroup1datarq=XX YY ZZ&group2field=KEY&wnGroup2datarq=YY will work as designed.My question on this whole search problem, then, is what are the values of [field1] and [field2]? Are they contradicting each other?Based on the wa / wn logic being applied to KEY, if [field2] contains a value that is not contained in [field1], then no results will be returned.Lawrence... Can you show us the values of [field1] and [field2]?- brian -- <= Brian C. Fries, BrainScan Software http://www.brainscansoftware.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:
see below...At 4:09 PM 10/25/02, Michael Davis wrote: >On Friday, October 25, 2002, at 12:23 PM, lb Lawrence wrote: > >>Hi, >> >>I have been going round and round with this problem. >> >>I have to search a db that have illegal HTML in the fields to search >> >>like bébé Thaïlande athléte >> >>I have tried >> >>[search db=admin/image.db[!] >>[/!]&group1field=KEY[!] >>[/!]&waGroup1datarq=[unurl][field1][/UnURL][!] >>[/!]&group2field=KEY[!] >>[/!]&wnGroup2datarq=[unurl][field2][/UnURL][!] >>[/!]&group3field=Orient[!] >>[/!]&woGroup3datarq=[Orient][!] >>[/!]&startat=[startat][!] >>[/!]&MAX=[MAX][!] >>[/!]&asDOSSIER_EDITEURsort=1[!] >>[/!]&asSKUsort=2] >> >>I thought [unurl] would fix my problem but nothing is working >> > >Do not use [unurl]. > >Problems with your search that I see... You are using grouping >without actually grouping any fields. You are also comparing the >same field more than once in the same search. The first problem may >work just fine, but is not necessary. The second problem will >absolutely break your search context. You cannot do two comparisons >on the KEY field like that. If you are saying KEY word-and = >field1, then use a [hideif [url][KEY][/url]=[url][field2][/url]] >within the [founditems] instead of the second KEY word-not field >comparison. > >Mike >Actually the method above does work in general and is specifically designed to allow you to search the same field two times.While you cannot say waKEYdatarq=XX YY ZZ&wnKEYdatarq=YY, as these both search a key field term named KEY, you can assign the field KEY to two different groups then search each group, thus effectively searching the same field twice.So, searching group1field=KEY&waGroup1datarq=XX YY ZZ&group2field=KEY&wnGroup2datarq=YY will work as designed.My question on this whole search problem, then, is what are the values of [field1] and [field2]? Are they contradicting each other?Based on the wa / wn logic being applied to KEY, if [field2] contains a value that is not contained in [field1], then no results will be returned.Lawrence... Can you show us the values of [field1] and [field2]?- brian -- <= Brian C. Fries, BrainScan Software http://www.brainscansoftware.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/
Brian Fries
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:
Beta less tested (was $flushcache causes crash) (2000)
WebCat2 beta 11 - new prefs ... (1997)
WebCat Redundancy (2000)
Email (1998)
Web Site (2000)
Re:Signal Raised (1997)
Blog solution (2006)
[WebDNA] WebDNA development (2017)
WebCat2b13MacPlugIn - [showif][search][/showif] (1997)
WebDNA 4.5.1 Now Available [OT] (2003)
Mail Service Dead (1998)
WebCat2b13MacPlugIn - More limits on [include] (1997)
The [shownext] limitations (2002)
PSC recommends what date format yr 2000??? (1997)
WCS Newbie question (1997)
vars (2000)
THANKS (1997)
Prevent multiple appends with Reload Button (1997)
Re:2nd WebCatalog2 Feature Request (1996)
FREE Stuff .. (2003)