| From: | Tim Pizey <timp(at)melati(dot)org> |
|---|---|
| To: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: how to continue using a connection after an error with autocommit=false |
| Date: | 2007-03-01 20:59:29 |
| Message-ID: | 200703012059.29908.timp@melati.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Wednesday 28 February 2007 22:33, Dave Cramer wrote:
> On 28-Feb-07, at 3:41 PM, Tim Pizey wrote:
> > On Tuesday 20 February 2007 10:50, Heikki Linnakangas wrote:
> >> James Im wrote:
> >>> I just find out that I cannot continue using a connection when I use
> >>> autocommit=false and that an sql insert failed.
> >>
> >> That's intended behavior in PostgreSQL.
> >
> > [snip]
> > This is new behaviour in version 8, I believe.
>
> No, this has been around since 7.x
>
> > I think this behaviour is unique to Postgresql?
>
> Possibly
>
> > Melati was developed with Postgresql version 6 as the target dbms
> > back in 2000, since then it has been extended to work with the
> > other common
> > dbmsen, but now it looks like it won't work with V8, without quite
> > a bit of
> > rework.
> >
Sorry, my bad, all Melati's tests pass on 8.1.4, without modification.
yours
Tim Pizey
--
http://melati.org/ - the flower of Java.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2007-03-01 23:35:32 | Re: Inserting "null" not working (Sun App Server, Postgres, EJB3)? |
| Previous Message | Heiko W.Rupp | 2007-03-01 20:48:00 | Re: Inserting "null" not working (Sun App Server, Postgres, EJB3)? |