Re: [WebDNA] MySQL float problems with WebDNA

This WebDNA talk-list message is from

2010


It keeps the original formatting.
numero = 104593
interpreted = N
texte = --0016368e28fc406587047e14108e Content-Type: text/plain; charset=ISO-8859-1 On Tue, Jan 26, 2010 at 5:51 AM, Toby Cox wrote: > Anyone experienced strange things happening with the float data type and > webdna? > > I have this code > > > [SQLConnect > dbType=MySQL&host=localhost&database=mysqldb&uid=myusername&pwd=mypassword&conn_var=conn1][/SQLConnect] > > > [SQLExecute conn_ref=conn1&result_var=mancodeAverage]SELECT * from > UR_mantotals WHERE mancode='[mancode]';[/SQLExecute] > > > [SQLResult > result_ref=mancodeAverage][founditems][perf][/founditems][/SQLResult] > > > 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 displaying > 1074655967 > > Using the same code, it will display all other fields properly ie: > > > ACTUAL DATA FROM MYSQL > ====================== > > FI 3.65934 3.74359 3.87179 3.33333 3.35897 3.71795 4.15385 3.4359 39 > > > DATA DISPLAYED BY WEBDNA > ======================== > > FI 1074611796 1074655967 1074655967 1074655967 1074655967 > 1074655967 1074655967 1074655967 1074655967 1074655967 > 1074655967 39 > > > > 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 > workaround for this. > > This issue was fixed in WebDNA 6.2 --0016368e28fc406587047e14108e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Tue, Jan 26, 2010 at 5:51 AM, Toby Cox <toby.cox@netro42.co= m> wrote:
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.

=A0
This issue was fixed in WebDNA 6.2
<= /div>

--0016368e28fc406587047e14108e-- Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] MySQL float problems with WebDNA (Toby Cox 2010)
  2. Re: [WebDNA] MySQL float problems with WebDNA (JJ WebDNA 2010)
  3. [WebDNA] MySQL float problems with WebDNA (Toby Cox 2010)
--0016368e28fc406587047e14108e Content-Type: text/plain; charset=ISO-8859-1 On Tue, Jan 26, 2010 at 5:51 AM, Toby Cox wrote: > Anyone experienced strange things happening with the float data type and > webdna? > > I have this code > > > [SQLConnect > dbType=MySQL&host=localhost&database=mysqldb&uid=myusername&pwd=mypassword&conn_var=conn1][/SQLConnect] > > > [SQLExecute conn_ref=conn1&result_var=mancodeAverage]SELECT * from > UR_mantotals WHERE mancode='[mancode]';[/SQLExecute] > > > [SQLResult > result_ref=mancodeAverage][founditems][perf][/founditems][/SQLResult] > > > 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 displaying > 1074655967 > > Using the same code, it will display all other fields properly ie: > > > ACTUAL DATA FROM MYSQL > ====================== > > FI 3.65934 3.74359 3.87179 3.33333 3.35897 3.71795 4.15385 3.4359 39 > > > DATA DISPLAYED BY WEBDNA > ======================== > > FI 1074611796 1074655967 1074655967 1074655967 1074655967 > 1074655967 1074655967 1074655967 1074655967 1074655967 > 1074655967 39 > > > > 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 > workaround for this. > > This issue was fixed in WebDNA 6.2 --0016368e28fc406587047e14108e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Tue, Jan 26, 2010 at 5:51 AM, Toby Cox <toby.cox@netro42.co= m> wrote:
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.

=A0
This issue was fixed in WebDNA 6.2
<= /div>

--0016368e28fc406587047e14108e-- JJ WebDNA

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:

CERT Advisory on malicious scripts (2000) WebCatalog 3.0.8 Mac OS (2000) syntax question, not in online refernce (1997) HomePage Caution (1997) Who is doing sign-ups-got it (1998) [shownext] (1999) Limitations on fields? Server is crashing (1997) Webcatalog/Butler (1998) [Sum] function? (1997) URGENT! ACGI Stopped!!!! (1997) Custom WebCat Prefs ... (1997) Re1000001: Setting up shop (1997) Can't Update records (1997) Database changes (1998) Calendar (1997) Am I going senile? (Price recalc based on quantity) (1997) Showing unopened cart (1997) [GROUPS] followup (1997) READFILE command? (1998) OS Limitations (1998)