Re: Search bug. Help
This WebDNA talk-list message is from 2002
It keeps the original formatting.
numero = 43499
interpreted = N
texte = That would be nice but my data type isn't wrong. I separate the values with a , or space in order to perform the search in the format that is expected by the search context. How else are you going to tell webcat that these are two distinct values be it text or num. I can assume that ww, ws and wa are all for searching text. Maybe some should be added for searching numericaly. Like numstarts with (ns), num contains (ns), and whole num (wn).As far as running 2 consecutive search to find 2 numeric values in the same field sounds a little silly.So basically there is no way to accomplish a simple search:[search db=mydb.db&woCTdatarq=.20,.25&CTword=ww&ctType=num]> I agree. It's a sad and sorry state when webcat bails out just > because it encounters a value that does not match the data type we > define for it. But that's exactly what it does. Or if you get lucky > and it does not bail out, it will simply respond with the wrong > data -- a situation that may be even worse than bailing out. > > A much better response would be for webcat to post an error message. > > An to make things even better, webcat could *also* create a sendmail > message that includes all the details we would need in order to find > and debug the problem -- just in case we (the administrators) are not > the ones who encounter the problem. > > For example, the email message could include: > > the db name > the field name > the value of the first field in that db (presumably this would be the > unique record identifier field, and this would make it easier for us > to identify the source of the non-matching data) > the template name > the ip address > the date > the time > the webcat version > the OS version > etc... > > ... and it should send this email message to the email address of the > webdna admin -- which could easily be stored in a new > webdnaAdminEmail preference and used not only in this situation, > but in other situations where it would be useful for a debugging > message to be delivered to the server administrator. > > > >> Sorry guys but I feel I gota add my two cents in here. >> >> This is another classic example of a typical - not so silly - coding >> mistake to make, that brings webcat to its knees. >> >> The engine should be more robust than this and should give feedback to the >> coder about the error they have made rather than hitting the fan. >> >> Error - line 14: you have specified an invallid data type, data type does >> not match record in database or casting not required for this search type. >> Click Here for help on data types. >> >> Something like this would be nice. >> >> But no... Webcat throws its toys out of the cot, takes its football and >> goes home. >> >> Anybody else have any thoughts on this? >> >> >>> 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/ >> >> >> >> >> >> Andrew Simpson >> Web Developer >> >> >> >> ------------------------------------------------------------- >> 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/ ------------------------------------------------------------- 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:
That would be nice but my data type isn't wrong. I separate the values with a , or space in order to perform the search in the format that is expected by the search context. How else are you going to tell webcat that these are two distinct values be it text or num. I can assume that ww, ws and wa are all for searching text. Maybe some should be added for searching numericaly. Like numstarts with (ns), num contains (ns), and whole num (wn).As far as running 2 consecutive search to find 2 numeric values in the same field sounds a little silly.So basically there is no way to accomplish a simple search:[search db=mydb.db&woCTdatarq=.20,.25&CTword=ww&ctType=num]> I agree. It's a sad and sorry state when webcat bails out just > because it encounters a value that does not match the data type we > define for it. But that's exactly what it does. Or if you get lucky > and it does not bail out, it will simply respond with the wrong > data -- a situation that may be even worse than bailing out. > > A much better response would be for webcat to post an error message. > > An to make things even better, webcat could *also* create a sendmail > message that includes all the details we would need in order to find > and debug the problem -- just in case we (the administrators) are not > the ones who encounter the problem. > > For example, the email message could include: > > the db name > the field name > the value of the first field in that db (presumably this would be the > unique record identifier field, and this would make it easier for us > to identify the source of the non-matching data) > the template name > the ip address > the date > the time > the webcat version > the OS version > etc... > > ... and it should send this email message to the email address of the > webdna admin -- which could easily be stored in a new > webdnaAdminEmail preference and used not only in this situation, > but in other situations where it would be useful for a debugging > message to be delivered to the server administrator. > > > >> Sorry guys but I feel I gota add my two cents in here. >> >> This is another classic example of a typical - not so silly - coding >> mistake to make, that brings webcat to its knees. >> >> The engine should be more robust than this and should give feedback to the >> coder about the error they have made rather than hitting the fan. >> >> Error - line 14: you have specified an invallid data type, data type does >> not match record in database or casting not required for this search type. >> Click Here for help on data types. >> >> Something like this would be nice. >> >> But no... Webcat throws its toys out of the cot, takes its football and >> goes home. >> >> Anybody else have any thoughts on this? >> >> >>> 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/ >> >> >> >> >> >> Andrew Simpson >> Web Developer >> >> >> >> ------------------------------------------------------------- >> 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/ ------------------------------------------------------------- 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:
Bug Report, maybe (1997)
Number of Open Databases (1998)
MacActivity and PCS (1997)
emailer w/F2 (1997)
YACBQ.....(Yet another checkbox question) (2000)
Pull Down Search (2000)
Repost: Orderfile, Grandtotal: How do I get it to all add up. (2000)
Webcat no longer supported? (2006)
any suggestions for creating a multi-lingual site? (1999)
OT: Portland Oregon (2002)
New Web Site Developers Database (1996)
Shownext from POST (2000)
Bad card db - *mislabled post* (1999)
searchable list archive (1997)
Grep two things at once? (2005)
[WebDNA] WebDNA Hosts (2009)
Express Lane (2000)
Multiple Stores and WebCatalog Prefs (1997)
Range Comparisons (2000)
Searching a database... (2003)