Thread: Strange JDBC error mesg
------SQL Exception !! ----- Error Message : Unable to fathom update count INSERT 2720759883 1 SQL State : null Error Code : 0 Any idea why I'm getting this? The queries been working fine for weeks and even now when I run it from psql, it runs without a hitch. But I've started to get this error when I run it from a Java program using JDBC. db version = 7.1.3 JDBC driver = from the same source tree. --Arsalan. ------------------------------------------------------------------- People often hate those things which they do not know, or cannot understand. --Ali Ibn Abi Talib (AS)
Arsalan, This is a bug in the driver that is already fixed in current sources. If you download the latest 7.2 driver from jdbc.postgresql.org you will have the fix for this bug. Basically the driver was storing the oid in an int. The value you have is overflowing the value allowed for a signed int. thanks, --Barry Arsalan Zaidi wrote: > ------SQL Exception !! ----- > Error Message : Unable to fathom update count INSERT 2720759883 1 > SQL State : null > Error Code : 0 > > Any idea why I'm getting this? The queries been working fine for weeks and > even now when I run it from psql, it runs without a hitch. But I've started > to get this error when I run it from a Java program using JDBC. > > db version = 7.1.3 > JDBC driver = from the same source tree. > > --Arsalan. > > > ------------------------------------------------------------------- > People often hate those things which they do not know, or cannot understand. > --Ali Ibn Abi Talib (AS) > > > ---------------------------(end of broadcast)--------------------------- > TIP 6: Have you searched our list archives? > > http://archives.postgresql.org > >
> Arsalan, > > This is a bug in the driver that is already fixed in current sources. > If you download the latest 7.2 driver from jdbc.postgresql.org you will > have the fix for this bug. > > Basically the driver was storing the oid in an int. The value you have > is overflowing the value allowed for a signed int. > The latest drivers cure all. Thanks a ton. --Arsalan.
> Basically the driver was storing the oid in an int. The value you have > is overflowing the value allowed for a signed int. > Just a small Q, what's the datatype now? --Arsalan