From: | Ryan Li <rleeuk(at)yahoo(dot)com> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | oid as long type |
Date: | 2006-02-08 09:47:44 |
Message-ID: | 20060208094744.74887.qmail@web34701.mail.mud.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
What's the reason of using int rather than long for the large object oid? I am experiencing a problem where the database server is generating oids exceeding the size for a Java int, and got "org.postgresql.util.PSQLException: Bad value for type int". Could this be solve by making org.postgresql.largeobject.LargeObject.oid a long type and make corresponding changes to the source tree?
(for example in org.postgresql.jdbc3.Jdbc3ResultSet.getBlob(int), instead of:
return new Jdbc3Blob(connection, getInt(i));
do:
return new Jdbc3Blob(connection, getLong(i));)
I am not familar with the internals of the driver, so not sure if there are other complications. Any advice on using long oids would be much appreciated.
Thanks in advance!
Ryan
From | Date | Subject | |
---|---|---|---|
Next Message | Achilleus Mantzios | 2006-02-08 10:57:30 | Re: oid as long type |
Previous Message | Markus Schaber | 2006-02-08 09:34:19 | Re: Inconsistent casting with literal vs parameter |