| 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:04:56 |
| Message-ID: | VisenaEmail.f9.f93505ffc59eaf2e.152f39d340c@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:51:47, skrev Sridhar N Bamandlapally <
sridhar(dot)bn1(at)gmail(dot)com <mailto:sridhar(dot)bn1(at)gmail(dot)com>>:
Ok, let me put this way
in JDBC we have setAutoCommit( false ) , and all dmls are independent
transactions
and when any transaction fails then the session not allowing next transactions
in Java when we do setAutoCommit( false ) its behaving like all transactions
in BEGIN-END block, this is not expected behavior
i guess this is bug
No, you got it backwards. With autocommit=false all statements are NOT
independent transactions.
-- 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 | Sridhar N Bamandlapally | 2016-02-18 09:20:51 | Re: JDBC behaviour |
| Previous Message | Sridhar N Bamandlapally | 2016-02-18 08:51:47 | Re: JDBC behaviour |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2016-02-18 09:19:08 | Re: Performance improvement for joins where outer side is unique |
| Previous Message | Sridhar N Bamandlapally | 2016-02-18 08:51:47 | Re: JDBC behaviour |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sridhar N Bamandlapally | 2016-02-18 09:20:51 | Re: JDBC behaviour |
| Previous Message | Sridhar N Bamandlapally | 2016-02-18 08:51:47 | Re: JDBC behaviour |