Re: search problem
This WebDNA talk-list message is from 2002
It keeps the original formatting.
numero = 45165
interpreted = N
texte = >Specifying Ad_Numbertype=num tells WebDNA to convert BOTh the >value of the field and the value to which it is being compared to >numbers prior to performing any comparisons or sorting.>>It appears to be the same as enclosing the values inside [math] >contexts, which gives results like this:>>value as num>234ab 234>a2 (blank)>33-ABC (blank)>123.45.67 123.45>000321 321>>So this generally wreaks havoc on any field that contains >non-numeric characters, and also eliminates any chance of a wo, >bw or similar comparison working. It can definitely screw up your >eq results as well - for example, with type=num, 123AB would match >00123XX, since the math would convert both values to 123.>>As a general rule, I do not use the type=num unless I need it for >sorting purposes.... and when you use it, make sure that none of the values you're searching for in that field are non-numeric. Because if they are non-numeric, your search will fail to find the records you might expect it to find.Sincerely,Kenneth Grome---------------------------------------------------WebDNA Professional Training and Development Center175 J. Llorente Street +63 (32) 255-6921Cebu City, Cebu 6000 kengrome@webdna.netPhilippines 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:
>Specifying Ad_Numbertype=num tells WebDNA to convert BOTh the >value of the field and the value to which it is being compared to >numbers prior to performing any comparisons or sorting.>>It appears to be the same as enclosing the values inside [math] >contexts, which gives results like this:>>value as num>234ab 234>a2 (blank)>33-ABC (blank)>123.45.67 123.45>000321 321>>So this generally wreaks havoc on any field that contains >non-numeric characters, and also eliminates any chance of a wo, >bw or similar comparison working. It can definitely screw up your >eq results as well - for example, with type=num, 123AB would match >00123XX, since the math would convert both values to 123.>>As a general rule, I do not use the type=num unless I need it for >sorting purposes.... and when you use it, make sure that none of the values you're searching for in that field are non-numeric. Because if they are non-numeric, your search will fail to find the records you might expect it to find.Sincerely,Kenneth Grome---------------------------------------------------WebDNA Professional Training and Development Center175 J. Llorente Street +63 (32) 255-6921Cebu City, Cebu 6000 kengrome@webdna.netPhilippines 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:
japanese characters (1997)
Problems with [Applescript] (1997)
Server slowing down. (1997)
Showif, Hideif reverse logic ? (1997)
WebCat2b12 - nesting [tags] (1997)
Showing once on a founditems (1997)
Frames and WebCat (1997)
[searchString] (1997)
Initiating NewCart (1997)
Sorting Results (1999)
email preferences on NT (1997)
email formatting (1999)
change the number format (1997)
WebMerchant 1.6 and https (1997)
WebDNA wholesale ... (2002)
Re:Searching for ALL / empty form field (1997)
Date Sorting (1997)
ErrorMessages.db (1998)
[UPPERCASE] (1997)
Remove from list server (1997)