| From: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
|---|---|
| To: | Sridhar N Bamandlapally <sridhar(dot)bn1(at)gmail(dot)com> |
| Cc: | Andreas Joseph Krogh <andreas(at)visena(dot)com>, List <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: JDBC behaviour |
| Date: | 2016-02-18 09:24:07 |
| Message-ID: | CAB=Je-FE-Gzp3N3U1X_r1ZEhe8FRkwO-vnOCMrMTd8cPiC09FQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers pgsql-jdbc |
Sridhar,
Please refer to documentation (see [1]).
Specification>Otherwise, its SQL statements are grouped into transactions
that are terminated by
Specification>a call to either the method commit or the method rollback
Sridhar> it should not be treating all next transactions as single set
What do you mean by "all next transactions"?
[1]:
https://docs.oracle.com/javase/7/docs/api/java/sql/Connection.html#setAutoCommit(boolean)
Vladimir
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Joseph Krogh | 2016-02-18 09:24:29 | Re: JDBC behaviour |
| Previous Message | Rakesh Kumar | 2016-02-18 09:23:50 | Re: Multiple databases and shared_buffers |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Joseph Krogh | 2016-02-18 09:24:29 | Re: JDBC behaviour |
| Previous Message | Sridhar N Bamandlapally | 2016-02-18 09:20:51 | Re: JDBC behaviour |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Joseph Krogh | 2016-02-18 09:24:29 | Re: JDBC behaviour |
| Previous Message | Sridhar N Bamandlapally | 2016-02-18 09:20:51 | Re: JDBC behaviour |