Bill,
Thank you for this. While that is true, the problem is that the number
in the database is actually 2 and not 4294967298. It seems the
connector/j is sticking that highest bit in there itself, or misbehaving
in some other way.
Apparently it has been fixed just hasn't been released yet:
http://bugs.mysql.com/bug.php?id=11940 I imagine 3.1.11 will have that
fix, whenever that will be released.
Thanks for your help and analysis,
Kevin
Bill Easton wrote:
What you are overlooking is that 4294967298 is outside the range of Java's
int--it's 0x100000002. So, when it's converted to int, the high order bit
gets discarded, and you are left with a result of 2. JDBC behaves as would
be expected.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
