From: | Travis Bauer <trbauer(at)indiana(dot)edu> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: InputStream as parameter not supported |
Date: | 2001-07-20 20:33:37 |
Message-ID: | 20010720153337.A17744@swell.cs.indiana.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Okay, I have found an old posting from Tom about setBytes that
said you had to use explicit begin and ends. So I started
sending explicit "BEGIN" and "COMMIT" statements to the backend
and it worked.
But why do you have to use explicit BEGIN and COMMIT statements
if you have autocommit turned off? I appearantly have to send
both a "COMMIT" statement to the back end and then execute the
Connection's commit() method to get the transactions committed.
Why is that?
Thanks,
--
----------------------------------------------------------------
Travis Bauer | CS Grad Student | IU |www.cs.indiana.edu/~trbauer
----------------------------------------------------------------
Travis Bauer (trbauer(at)indiana(dot)edu) wrote:
> I'm using the JDBC driver 7.1. I'm trying to write data into
> prepared statements using InputStreams. When I use the sample
> program with a simple example, it works great. When I use the
> 'real world' code, I get the above error.
>
> Are there any known flaws or exceptions in the 7.1 JDBC driver that would
> occassionally produce the "InputStream as parameter not supported"
> error?
>
> Thanks
>
From | Date | Subject | |
---|---|---|---|
Next Message | IRWIN,KEITH (Non-HP-Corvallis,ex1) | 2001-07-20 20:51:04 | Does dropping a column from a table mess up foreign keys? |
Previous Message | Tom Lane | 2001-07-20 20:33:17 | Re: RPM source files should be in CVS (was Re: psql -l) |