| From: | Andreas Joseph Krogh <andreas(at)visena(dot)com> |
|---|---|
| To: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: JDBC behaviour |
| Date: | 2016-02-18 09:24:29 |
| Message-ID: | VisenaEmail.fd.a0847dd522e46d81.152f3b0448d@tc7-visena |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers pgsql-jdbc |
På torsdag 18. februar 2016 kl. 10:20:51, skrev Sridhar N Bamandlapally <
sridhar(dot)bn1(at)gmail(dot)com <mailto:sridhar(dot)bn1(at)gmail(dot)com>>:
setAutoCommit(false), it should not be treating all next transactions as
single set, simple, this is what expected behavior
The point is that all subsequent statements (after an exception) are part of
the same transaction (in autocommit=false mode). So you have to issue an
explicit ROLLBACK before any new statement can give meaningful results.
-- Andreas Joseph Krogh
CTO / Partner - Visena AS
Mobile: +47 909 56 963
andreas(at)visena(dot)com <mailto:andreas(at)visena(dot)com>
www.visena.com <https://www.visena.com>
<https://www.visena.com>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John R Pierce | 2016-02-18 09:34:38 | Re: [JDBC] JDBC behaviour |
| Previous Message | Vladimir Sitnikov | 2016-02-18 09:24:07 | Re: JDBC behaviour |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John R Pierce | 2016-02-18 09:34:38 | Re: [JDBC] JDBC behaviour |
| Previous Message | Vladimir Sitnikov | 2016-02-18 09:24:07 | Re: JDBC behaviour |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John R Pierce | 2016-02-18 09:34:38 | Re: [JDBC] JDBC behaviour |
| Previous Message | Vladimir Sitnikov | 2016-02-18 09:24:07 | Re: JDBC behaviour |