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
Kevin,
What you are overlooking is that 4294967298 is outside the range of Java's
int--it's 0x10002. 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.
public class TestLong {
final public static voi
