Skip site navigation (1) Skip section navigation (2)

Re: "Unable to fathom update count" - what does it mean?

From: Barry Lind <barry(at)xythos(dot)com>
To: Graham Leggett <minfrin(at)sharp(dot)fm>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: "Unable to fathom update count" - what does it mean?
Date: 2001-11-25 23:46:55
Message-ID: 3C0182EF.5020400@xythos.com (view raw or flat)
Thread:
Lists: pgsql-jdbc
Graham,

This bug is now fixed in current sources.  The fix did not make it into 
7.2beta3.  I have placed new builds up on jdbc.postgresql.org that you 
can download, or you can pull the code from cvs and built it yourself.

thanks,
--Barry

 From CVS changelog:
This patch fixes a bug reported by Graham Leggett (minfrin(at)sharp(dot)fm).
The bug was that any insert or update would fail if the returned oid was
larger than a signed int.  Since OIDs are unsigned int's it was
a bug that the code used a java signed int to deal with the values.  The bug
would result in the error message: "Unable to fathom update count".
While fixing the bug, it became apparent that other code made a similar
assumption about OIDs being signed ints.  Therefore some methods that 
returned
or took OIDs are arguements also needed to be changed.
Since we are so close to the 7.2 release I have added new methods that
return longs and deprecated the old methods returning ints.  Therefore all
old code should still work without requiring a code change to cast from 
long to int.  Also note that the methods below are PostgreSQL specific 
extensions to
the JDBC api are are not part of the spec from Sun, thus it is unlikely that
they are used much or at all.

The deprecated methods are:
   ResultSet.getInsertedOID()
   Statement.getInsertedOID()
   Serialize.store()
   Connection.putObject()
and are replaced by:
   ResultSet.getLastOID()
   Statement.getLastOID()
   Serialize.storeObject()
   Connection.storeObject()
All the deprecated methods returned int, while their replacements return 
long

This patch also fixes two comments in MD5Digest that the author Jeremy Wohl
submitted.




Graham Leggett wrote:

> Hi all,
> 
> I have a server which has started giving a weird error during a database
> INSERT:
> 
>   Unable to fathom update count INSERT 3523561677 1
> 
> I have an identical setup on a staging server that does not show this
> problem - however before I can try do something about it I need to
> understand just what this error message is trying to tell me.
> 
> I have trawled documentation and mailing lists, however it seems there
> is no description anywhere of the error messages within the Postgrsql
> JDBC driver. Does this info exist anywhere?
> 
> Can anyone explain to me what this error is trying to tell me?
> 
> Regards,
> Graham
> 



In response to

pgsql-jdbc by date

Next:From: Mihael VrbanecDate: 2001-11-26 01:25:48
Subject: Problems with truncated BLOBs
Previous:From: Dhruv PandyaDate: 2001-11-25 21:18:16
Subject: JDBC driver 7.1 and Kerberos 5

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group