MYSQL 4.1 INT datatype issues with CF7

[rwhaun]

When I try to pull my SMALLINT, MEDIUMINT, and INT fields from my MYSQL 4.1
tables, I get a value like "4294967307". However, once I change the datatypes
to BIGINT, they work just fine and I can pull the actual values.

I am running ColdFusion MX 7 with hotfix3 and the latest MYSQL JDBC driver. I
have seen this problem on my Windows 2003 CF7 installation as well as when
running it locally as the standalone 8500 installation. It isn't isolated to
one table or datasource, it happens in them all.

Also, for the record, the exact same cfqueries and mysql tables work fine with
CFMX 6.1. I am in the process of migrating to MX7 though.

Any suggestions? This isn't a major problem, I've just been chaning all my
datatypes to BIGINT and things work fine.

William Haun - haunw@at@spcollege)dot(com

[Neculai Macarie]

> When I try to pull my SMALLINT, MEDIUMINT, and INT fields from my MYSQL
4.1

> tables, I get a value like "4294967307". However, once I change the

datatypes

> to BIGINT, they work just fine and I can pull the actual values.
>
> I am running ColdFusion MX 7 with hotfix3 and the latest MYSQL JDBC

driver. I

> have seen this problem on my Windows 2003 CF7 installation as well as when
> running it locally as the standalone 8500 installation. It isn't isolated

to

> one table or datasource, it happens in them all.
>
> Also, for the record, the exact same cfqueries and mysql tables work fine

with

> CFMX 6.1. I am in the process of migrating to MX7 though.
>
> Any suggestions? This isn't a major problem, I've just been chaning all

my

> datatypes to BIGINT and things work fine.

I think I had the same problem and I solved it by upgrading to the latest
jdbc driver (from the 3.2 series).

--
<mack />

[rwhaun]

Thanks for the tip. I downloaded the
[url]http://dev.mysql.com/downloads/connector/j/3.2.html[/url] and it solved the problem.
Unfortunately, that version is still in ALPHA phase so I'm a bit wary about
using it in production.

For now, I may just continue with my workaround until a stable version of JDBC
3.2 is released.

Anyone think I should submit this as a bug report for CFMX7? or is it a MYSQL
JDBC bug? I didn't have the problem with JDBC 3.1 on CFMX6.1. So that makes
me think it is more of a CF7 issue.

[mpwoodward *TMM*]

rwhaun wrote:

> Thanks for the tip. I downloaded the
> [url]http://dev.mysql.com/downloads/connector/j/3.2.html[/url] and it solved the problem.
> Unfortunately, that version is still in ALPHA phase so I'm a bit wary about
> using it in production.
>
> For now, I may just continue with my workaround until a stable version of JDBC
> 3.2 is released.
>
> Anyone think I should submit this as a bug report for CFMX7? or is it a MYSQL
> JDBC bug? I didn't have the problem with JDBC 3.1 on CFMX6.1. So that makes
> me think it is more of a CF7 issue.
>

This sounds to me like a driver issue--if using a new driver fixes the
problem, then it's definitely the JDBC driver, not CF.

Matt

--
Matt Woodward
[email]mpwoodward@gmail.com[/email]
Team Macromedia - ColdFusion