[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:
[Announce] Newest Commerce Site based on WebCatalog (1997)
FISKARS (2003)
Multiple postings (2000)
[WriteFile] problems (1997)
best way to test for the existence of a parameter in a url (2003)
Is there a max number of fields? (1998)
append=T problem (1998)
Shipping Formula % (2003)
process SSI (1998)
[OT] Satellite (2005)
Nested [SEARCH] and [REPLACE] problem. (1997)
WebCat2b14MacPlugIn - [include] doesn't hide the search string (1997)
Totally ignored by Smithmicro (2004)
URL for Discussion Archive (1997)
Trunk-gator (1997)
Time/date formatting %X doesn't work ... (1997)
Template transformed itself into a database? (1998)
docs for WebCatalog2 (1997)
Emailer issue (2006)
New commands in Final candidate (1997)