[WebDNA] Is [math] on a number with too many digits the only way that I can get scientific notation out of webdna?
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 106985
interpreted = N
texte = Hi everyonesome legacy code in one client's very large system was doing manual =incrementing (not using the AUTONUMBER param) on a numeric uniqueID =field as a way to generate the next ID for appending records.. and that =was OK in olden days.. when there was less traffic.. but now it can =happen that two people can cause the file to fire simultaneously .. each =trying to run before the other is finished.. causing the uniqueID which =gets generated to be a dupe on occasion. So we replaced every place we =could find such code with code that uses [cart] strings instead of the =plain incrementing number.. (so the uniqueID]s become cart strings.. =and all should be happy-ever-after... BUT there is (I am guessing) =still some code somewhere (which we have not yet found) that is trying =to increment (+1) to that field.. and when it now happens to be a cart =number (which is a number with a lot of digits), then the result of the =[math] operation (incrementing code) is scientific notation. (i.e. ="1.31108545312375e+16")... and that is causing some problems =elsewhere..so besides us just needing to find any remaining places where code is =trying to increment that field value.. I also thought it timely to ask =here:Is doing [math] on a number with too many digits the only way any of you =has seen webdna generate scientific notation? ...Or how else?the only way *I* know of, to cause that, is like so:this:[math][cart]+1[/math]produces:1.31108545312375e+16Is there any other way that I can get scientific notation out of webdna?Thanks-Govinda=
Associated Messages, from the most recent to the oldest:
Hi everyonesome legacy code in one client's very large system was doing manual =incrementing (not using the AUTONUMBER param) on a numeric uniqueID =field as a way to generate the next ID for appending records.. and that =was OK in olden days.. when there was less traffic.. but now it can =happen that two people can cause the file to fire simultaneously .. each =trying to run before the other is finished.. causing the uniqueID which =gets generated to be a dupe on occasion. So we replaced every place we =could find such code with code that uses
[cart] strings instead of the =plain incrementing number.. (so the uniqueID]s become cart strings.. =and all should be happy-ever-after... BUT there is (I am guessing) =still some code somewhere (which we have not yet found) that is trying =to increment (+1) to that field.. and when it now happens to be a cart =number (which is a number with a lot of digits), then the result of the =
[math] operation (incrementing code) is scientific notation. (i.e. ="1.31108545312375e+16")... and that is causing some problems =elsewhere..so besides us just needing to find any remaining places where code is =trying to increment that field value.. I also thought it timely to ask =here:Is doing
[math] on a number with too many digits the only way any of you =has seen webdna generate scientific notation? ...Or how else?the only way *I* know of, to cause that, is like so:this:
[math][cart]+1[/math]produces:1.31108545312375e+16Is there any other way that I can get scientific notation out of webdna?Thanks-Govinda=
Govinda
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:
No Data Results (1997)
Using WebCat for product info requests (1997)
WC 2.0 frames feature (1997)
Search in 2 or more catalogs (1997)
Almost a there but..bye bye NetCloak (1997)
Wrong person (1998)
Drop Down Menus (2002)
Content-type:... (2000)
Nested tags count question (1997)
question: back button prevention (1997)
Max Record length restated as maybe bug (1997)
Searching a field and returning the highest value (1997)
[WebDNA] Processor Maxing out (2010)
[defined]ish (1997)
[WebDNA] Fails to recognize comma-separated db (2010)
what does [url] copy [/url] really do? (2000)
Search Engine questions ... (2002)
WebCat2b14MacPlugIn - [include] doesn't hide the search string (1997)
WebDNA Server Not Running (2005)
Delete Context - to remove record (1998)