Anyone experienced strange things happening with the float data type and we=bdna?
I have this code
<!-- First connect up to the MySQL DB -->
[SQLConnect dbType=3DMySQL&host=3Dlocalhost&database=3Dmysqldb&=uid=3Dmyusername&pwd=3Dmypassword&conn_var=3Dconn1][/SQLConnect]
<!-- The execute my statement -->
[SQLExecute conn_ref=3Dconn1&result_var=3DmancodeAverage]SELECT * from =UR_mantotals WHERE mancode=3D'[mancode]';[/SQLExecute]
<!-- Retrieve results -->
[SQLResult result_ref=3DmancodeAverage][founditems][perf][/founditems][/SQL=Result]
The table UR_mantotals has 10 fields, one is a char(2) field, 8 are float, =and 1 is int(8)
Now, in the example above, perf is a float data type and although my MySQL =GUI app tells me that the real stored value is 3.65934, webDNA is displayin=g 1074655967
Using the same code, it will display all other fields properly ie:
ACTUAL DATA FROM MYSQL
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
FI =A0 =A0 =A03.65934 3.74359 3.87179 3.33333 3.35897 3.71795 4.15385 3.435=9 =A039
DATA DISPLAYED BY WEBDNA
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
FI 1074611796 =A0 1074655967 =A0 =A0 =A01074655967 =A0 =A0 =A01074655967 10=74655967 =A0 1074655967 =A0 =A0 =A01074655967 =A0 =A0 =A01074655967 1074655=967 =A0 1074655967 =A0 =A0 =A01074655967 =A0 =A0 =A039
As you can see, the int and char fields are fine, but the float types have =gone loopy. Has anyone experienced similar? Is this a bug?
The float data type is required for this project, so I can't see a work=around for this.
|
Anyone experienced strange things happening with the float data type and we=bdna?
I have this code
<!-- First connect up to the MySQL DB -->
[SQLConnect dbType=3DMySQL&host=3Dlocalhost&database=3Dmysqldb&=uid=3Dmyusername&pwd=3Dmypassword&conn_var=3Dconn1][/SQLConnect]
<!-- The execute my statement -->
[SQLExecute conn_ref=3Dconn1&result_var=3DmancodeAverage]SELECT * from =UR_mantotals WHERE mancode=3D'[mancode]';[/SQLExecute]
<!-- Retrieve results -->
[SQLResult result_ref=3DmancodeAverage][founditems][perf][/founditems][/SQL=Result]
The table UR_mantotals has 10 fields, one is a char(2) field, 8 are float, =and 1 is int(8)
Now, in the example above, perf is a float data type and although my MySQL =GUI app tells me that the real stored value is 3.65934, webDNA is displayin=g 1074655967
Using the same code, it will display all other fields properly ie:
ACTUAL DATA FROM MYSQL
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
FI =A0 =A0 =A03.65934 3.74359 3.87179 3.33333 3.35897 3.71795 4.15385 3.435=9 =A039
DATA DISPLAYED BY WEBDNA
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
FI 1074611796 =A0 1074655967 =A0 =A0 =A01074655967 =A0 =A0 =A01074655967 10=74655967 =A0 1074655967 =A0 =A0 =A01074655967 =A0 =A0 =A01074655967 1074655=967 =A0 1074655967 =A0 =A0 =A01074655967 =A0 =A0 =A039
As you can see, the int and char fields are fine, but the float types have =gone loopy. Has anyone experienced similar? Is this a bug?
The float data type is required for this project, so I can't see a work=around for this.
DOWNLOAD WEBDNA NOW!
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...