This driver have bug in working with BIG_INT8.
Check nntp server msnews.microsoft.com
There exists group about this driver
On the newsgroup they suggested the use of 'long' to handle the BIGINT values. However, the mapping already looks like this. I am not sure if this attempts to do what they suggested on the newsgroup:
Also, how do we change the defaults for the CMP fields? For instance, how could I change the default value of BIGINT(8) to INT or something when the tables are created? Thanks
there is a bug in MS drivers. If you change your type of your column to nullable, everything should be fine. Errors occurs only if column has type 'Long' and declare as 'NOT NULL'.
Great - thank you very much for your replies. I was able to change the code to have the primary key's use int's as opposed to Long's. One thought I had though, would it work just to map the Long datatype to the FLOAT JDBC type as opposed to the BIGINT type - they are both 8 byte values.