| From: | Peter T Mount <peter(at)retep(dot)org(dot)uk> |
|---|---|
| To: | KB Sriram <kbs(at)snapfish(dot)com> |
| Cc: | "'pgsql-jdbc(at)postgresql(dot)org'" <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: |
| Date: | 2001-02-12 14:25:31 |
| Message-ID: | 981987931.3a87f25b9f790@webmail.retep.org.uk |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Quoting KB Sriram <kbs(at)snapfish(dot)com>:
> I'm using the 7.0.3 release JDBC driver, and observed that when
> Postgres aborts the transaction because of a problem within a
> transaction block, SQLExceptions are not always thrown from the
> driver on further queries.
[snip]
> Looking into the code, it looked as though the *ABORT STATUS* message
> in the protocol was being ignored in the driver. I've attached a patch
> (against the 7.0.3 driver) of the changes that made it work better
> for me.
[snip]
I'll apply this when I get back to my source tree.
Peter
--
Peter Mount peter(at)retep(dot)org(dot)uk
PostgreSQL JDBC Driver: http://www.retep.org.uk/postgres/
RetepPDF PDF library for Java: http://www.retep.org.uk/pdf/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2001-02-12 17:25:37 | Re: Re: PostgreSQL and PHP persistent connections |
| Previous Message | Peter T Mount | 2001-02-12 11:49:00 | Status of JDBC web site |