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

RE: JDBC and LO - invalid large object descriptor

From: Dnesbitt(at)encryptix(dot)com
To: Andreas(dot)Vogler(at)geneon(dot)de
Cc: Dnesbitt(at)encryptix(dot)com, pgsql-interfaces(at)postgresql(dot)org
Subject: RE: JDBC and LO - invalid large object descriptor
Date: 2000-09-29 02:20:55
Message-ID: 19016070071ED411B61300508BAC4B75041A61@exch1etix.encryptix.com (view raw or flat)
Thread:
Lists: pgsql-interfaces
Andreas,

Are you doing the following prior to your executeQuery() method call?

            conn.setAutoCommit(false);

If not, then I think that may be your problem.  It may seem weird to do a
query in a transaction, but that is how it works.

Regards,
//Dave

> -----Original Message-----
> From: Andreas Vogler [mailto:Andreas(dot)Vogler(at)geneon(dot)de]
> Sent: Sunday, September 24, 2000 6:29 AM
> To: pgsql-interfaces(at)postgresql(dot)org
> Subject: [INTERFACES] JDBC and LO - invalid large object descriptor
> 
> 
> Hi,
> 
> I have got a problem with reading large objects from Postgres 
> through JDBC
> (both 7.0.2):
> a call to resultset.getBytes(...) results in:
> 
> FastPath call returned ERROR:  lo_tell: invalid large object 
> descriptor (0)
> at org.postgresql.fastpath.Fastpath.fastpath(Fastpath.java:141)
> at org.postgresql.fastpath.Fastpath.fastpath(Fastpath.java:191)
> at org.postgresql.fastpath.Fastpath.getInteger(Fastpath.java:203)
> at org.postgresql.largeobject.LargeObject.tell(LargeObject.java:232)
> at org.postgresql.largeobject.LargeObject.size(LargeObject.java:247)
> at org.postgresql.jdbc2.ResultSet.getBytes(ResultSet.java:370)
> 
> using "select lo_export(...)" is no problem, so I suppose the 
> data is stored
> correctly within the DB.
> Any idea where the 0 is comming from or what the problem could be?
> 
> Bye
> 	Andreas
> 

Responses

pgsql-interfaces by date

Next:From: James OrrDate: 2000-09-29 07:17:35
Subject: ODBC with version 7.0.2
Previous:From: Ken KachnowichDate: 2000-09-28 22:07:52
Subject: Re: Newlines in String inserts with JDBC

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