Re: Negative Range Error
This WebDNA talk-list message is from 2003
It keeps the original formatting.
numero = 48814
interpreted = N
texte = I ran some tests using 4.5.0 on OSX and found that I cannot search for negative numbers at all when I specify type=num.I created range.db: id value 1 one 10 ten 200 two hundred -50 negative 50 -200 negative 200 73 seventy-three -17 negative 17and tried searching: [search db=[tRoot]test/range.db&eqIDdatarq=-17&idType=num] [founditems][id] - [value]
[/founditems][/search]... and got nothing.I tried it with [url] around the -17, and still got nothing.I tried it with the value 73 instead and got a valid result.I tried it with -17 and type=text and found the -17 record.I tried it with a range, both via the rn method and the mr / xr method and it works fine with positive numbers, but not with negative numbers.My conclusion: WebDNA does not search properly for negative numbers when using type=num. And clearly, except for eq and ne tests, searching with type=text is not helpful.- (the other) Brian-- Brian Fries, BrainScan Software -- http://www.brainscansoftware.com -- On Thursday, March 20, 2003, at 07:05 AM, Brian Boegershausen wrote:> Well I have added in the wbrk= > and it is still not working. It works fine with positive coordinants, > but > once a negative is introduced, it is a problem. > I have tried switching the two numbers in the range also and it is > still > giving me an error. > I am running WebDNA 4.0.2 > > Is this a bug? > Can someone tell me if this works in 4.5 becuase I will upgrade > immediately > if it is. > > SMSI.... your thoughts on this. > > > Brian > > ----- Original Message ----- > From: Tim Robinson
> To: WebDNA Talk > Sent: Wednesday, March 19, 2003 5:25 PM > Subject: Re: Negative Range Error > > >> Well, according to the docs: When specifying a range, the smaller >> value >> must precede the larger value. Bit vague that in terms of negatives. >> I >> would assume that the larger negative number would need to go first. >> But >> apart from that theorising, I'm wondering if it would help to put in a > wbrk >> delimiter. Because you have a '-' and a '.' it might help to specify a > wbrk >> that is different to that. >> >> Unfortunately I have no idea whether a negative value is even >> allowed... >> >> Regards, >> Tim >> -- >> Tim Robinson >> IDFK Web Developments >> tim@idfk.com.au >> 114a/40 Yeo Street >> Neutral Bay 2089 >> Australia >> Phone +612 9908 2134 >> Fax +612 9908 4837 >> >>> From: Brian Boegershausen >>> Reply-To: (WebDNA Talk) >>> Date: Wed, 19 Mar 2003 16:31:39 >>> To: (WebDNA Talk) >>> Subject: Negative Range Error >>> >>> Has anyone successfully written code to do a search using the range > function >>> that has negative numbers? >>> >>> I am having many problems getting my search working for finding the > radius >>> around a zip code by latitude and longitude. >>> It works find for long/lats that are not negative numbers, but once I >>> introduct a - in there, I do not get any results. >>> >>> Here is my search: >>> >>> db=coordinants.db&rnLATITUDEdatarq=47.391072 >>> > 47.680736&rnLONGITUDEdatarq=-52.998186 > -53.427236&LATITUDEtype=num&LONGITUDE >>> type=num&asSTATEsort=1&asZIPCODEsort=2&ZIPCODEsumm=T >>> >>> >>> I get the same bad results if I switch the 2 coordinants in the > longitude >>> around. >>> I had a thought of just getting rid of the - signs in there, but >>> some of > my >>> coordinants are around the pos neg border and it will not produce the >>> correct results. >>> >>> Brian > ------------------------------------------------------------- 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://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
I ran some tests using 4.5.0 on OSX and found that I cannot search for negative numbers at all when I specify type=num.I created range.db: id value 1 one 10 ten 200 two hundred -50 negative 50 -200 negative 200 73 seventy-three -17 negative 17and tried searching: [search db=[tRoot]test/range.db&eqIDdatarq=-17&idType=num] [founditems][id] - [value]
[/founditems][/search]... and got nothing.I tried it with [url] around the -17, and still got nothing.I tried it with the value 73 instead and got a valid result.I tried it with -17 and type=text and found the -17 record.I tried it with a range, both via the rn method and the mr / xr method and it works fine with positive numbers, but not with negative numbers.My conclusion: WebDNA does not search properly for negative numbers when using type=num. And clearly, except for eq and ne tests, searching with type=text is not helpful.- (the other) Brian-- Brian Fries, BrainScan Software -- http://www.brainscansoftware.com -- On Thursday, March 20, 2003, at 07:05 AM, Brian Boegershausen wrote:> Well I have added in the wbrk= > and it is still not working. It works fine with positive coordinants, > but > once a negative is introduced, it is a problem. > I have tried switching the two numbers in the range also and it is > still > giving me an error. > I am running WebDNA 4.0.2 > > Is this a bug? > Can someone tell me if this works in 4.5 becuase I will upgrade > immediately > if it is. > > SMSI.... your thoughts on this. > > > Brian > > ----- Original Message ----- > From: Tim Robinson > To: WebDNA Talk > Sent: Wednesday, March 19, 2003 5:25 PM > Subject: Re: Negative Range Error > > >> Well, according to the docs: When specifying a range, the smaller >> value >> must precede the larger value. Bit vague that in terms of negatives. >> I >> would assume that the larger negative number would need to go first. >> But >> apart from that theorising, I'm wondering if it would help to put in a > wbrk >> delimiter. Because you have a '-' and a '.' it might help to specify a > wbrk >> that is different to that. >> >> Unfortunately I have no idea whether a negative value is even >> allowed... >> >> Regards, >> Tim >> -- >> Tim Robinson >> IDFK Web Developments >> tim@idfk.com.au >> 114a/40 Yeo Street >> Neutral Bay 2089 >> Australia >> Phone +612 9908 2134 >> Fax +612 9908 4837 >> >>> From: Brian Boegershausen >>> Reply-To: (WebDNA Talk) >>> Date: Wed, 19 Mar 2003 16:31:39 >>> To: (WebDNA Talk) >>> Subject: Negative Range Error >>> >>> Has anyone successfully written code to do a search using the range > function >>> that has negative numbers? >>> >>> I am having many problems getting my search working for finding the > radius >>> around a zip code by latitude and longitude. >>> It works find for long/lats that are not negative numbers, but once I >>> introduct a - in there, I do not get any results. >>> >>> Here is my search: >>> >>> db=coordinants.db&rnLATITUDEdatarq=47.391072 >>> > 47.680736&rnLONGITUDEdatarq=-52.998186 > -53.427236&LATITUDEtype=num&LONGITUDE >>> type=num&asSTATEsort=1&asZIPCODEsort=2&ZIPCODEsumm=T >>> >>> >>> I get the same bad results if I switch the 2 coordinants in the > longitude >>> around. >>> I had a thought of just getting rid of the - signs in there, but >>> some of > my >>> coordinants are around the pos neg border and it will not produce the >>> correct results. >>> >>> Brian > ------------------------------------------------------------- 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://webdna.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:
Upload Maximum (2003)
Running _every_ page through WebCat ? (1997)
3.08 installer (2003)
more multiple items to shopping cart (2000)
Dummy Credit Card Number for debug? (1997)
RE: [WebDNA] Ubuntu and WebDNA (2019)
Grepping a csv (2003)
Separate SSL Server (1997)
oops private message leaked into talk list (1997)
Using Applescript to process WebCatalog functions (1998)
[include ...] behavior (1997)
Emailer error 571 (1998)
More on the email templates (I like it) (1997)
ignore this test (1999)
service stop and restart (1997)
format search comparison Q (2000)
WC 2.0 frames feature (1997)
Shed some light on web delivery? (2000)
2.0Beta Command Ref (can't find this instruction) (1997)
2.0Beta Command Ref (can't find this instruction) (1997)