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

RE: JDBC - setAsciiStream - how to support?

From: Peter Mount <petermount(at)maidstone(dot)gov(dot)uk>
To: "'George Henry C(dot) Daswani'" <gdaswani(at)marketgroups(dot)com>, pgsql-interfaces(at)postgresql(dot)org
Subject: RE: JDBC - setAsciiStream - how to support?
Date: 2000-11-02 10:25:51
Message-ID: 1B3D5E532D18D311861A00600865478CF1B4C2@exchange1.nt.maidstone.gov.uk (view raw or flat)
Thread:
Lists: pgsql-interfaces
You must turn off AutoCommit before any large object call using
setAutoCommit(false);
 
Peter

-- 
Peter Mount 
Enterprise Support Officer, Maidstone Borough Council 
Email: petermount(at)maidstone(dot)gov(dot)uk 
WWW: http://www.maidstone.gov.uk <http://www.maidstone.gov.uk/>  
All views expressed within this email are not the views of Maidstone Borough
Council 

-----Original Message-----
From: George Henry C. Daswani [mailto:gdaswani(at)marketgroups(dot)com]
Sent: Thursday, November 02, 2000 7:32 AM
To: pgsql-interfaces(at)postgresql(dot)org
Subject: [INTERFACES] JDBC - setAsciiStream - how to support?


Hello,
 
    I've taken a look at the JDBC driver (from www.retep.org.uk
<http://www.retep.org.uk> ) - tried the jdbc7.1-1.2.jar
and the jdbc7.0-1.1.jar
 
Both doesn't seem to support the setAsciiStream
jdbc2 PreparedStatement accessor..
 
I tried using setBytes instead under a transaction block
(setAutoCommit(false)), ie..
 
ps.setBytes(9,this.description.trim().getBytes())
 
but an error shows up,
 
FastPath call returned ERROR: lo_write: invalid large obj descriptor (0);
 
Any ideas?

pgsql-interfaces by date

Next:From: Peter MountDate: 2000-11-02 10:27:45
Subject: RE:
Previous:From: Peter MountDate: 2000-11-02 10:25:01
Subject: RE: using large objects with jdbc

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