| From: | Andreas Joseph Krogh <andreas(at)visena(dot)com> |
|---|---|
| To: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: JDBC behaviour |
| Date: | 2016-02-18 10:59:50 |
| Message-ID: | VisenaEmail.10a.1f49c7f5f62b57b3.152f4086070@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. 11:43:36, skrev Sridhar N Bamandlapally <
sridhar(dot)bn1(at)gmail(dot)com <mailto:sridhar(dot)bn1(at)gmail(dot)com>>:
The code/framework is written to handle batch inserts, which is common for all
databases
I feel, PostgreSQL JDBC may need to modify setAutoCommit(false) code to
"implicit savepoint - on error - rollback to savepoint"
You simply cannot have batch-inserts in the same transaction and expecting the
batch not to fail if one of the statements in the batch fails.
-- 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 | Andreas Joseph Krogh | 2016-02-18 11:02:00 | Re: JDBC behaviour |
| Previous Message | Dave Cramer | 2016-02-18 10:52:03 | Re: JDBC behaviour |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Joseph Krogh | 2016-02-18 11:02:00 | Re: JDBC behaviour |
| Previous Message | Dave Cramer | 2016-02-18 10:52:03 | Re: JDBC behaviour |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Joseph Krogh | 2016-02-18 11:02:00 | Re: JDBC behaviour |
| Previous Message | Dave Cramer | 2016-02-18 10:52:03 | Re: JDBC behaviour |