| From: | Andreas Joseph Krogh <andreas(at)visena(dot)com> |
|---|---|
| To: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: JDBC behaviour |
| Date: | 2016-02-18 08:30:27 |
| Message-ID: | VisenaEmail.f3.8cfd0e7e391ce0a2.152f37ec294@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. 09:26:59, skrev Sridhar N Bamandlapally <
sridhar(dot)bn1(at)gmail(dot)com <mailto:sridhar(dot)bn1(at)gmail(dot)com>>:
If we want transactions in "begin-end" then its fine,
but in this case all these transactions are independent with autocommit off,
user choice to continue with commit or rollback
Look in you serverlogs, "something" is issuing a BEGIN. The transaction
becomes invalid when an error occurs, you have to issue a COMMIT or ROLLBACK,
and in this case both will ROLLBACK.
-- 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 | Vladimir Sitnikov | 2016-02-18 08:30:49 | Re: JDBC behaviour |
| Previous Message | Sridhar N Bamandlapally | 2016-02-18 08:26:59 | Re: JDBC behaviour |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vladimir Sitnikov | 2016-02-18 08:30:49 | Re: JDBC behaviour |
| Previous Message | Andres Freund | 2016-02-18 08:30:17 | Re: exposing pg_controldata and pg_config as functions |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vladimir Sitnikov | 2016-02-18 08:30:49 | Re: JDBC behaviour |
| Previous Message | Sridhar N Bamandlapally | 2016-02-18 08:26:59 | Re: JDBC behaviour |