| From: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
|---|---|
| To: | Sridhar N Bamandlapally <sridhar(dot)bn1(at)gmail(dot)com> |
| Cc: | PG-General Mailing List <pgsql-general(at)postgresql(dot)org>, List <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: [JDBC] JDBC behaviour |
| Date: | 2016-02-18 08:13:39 |
| Message-ID: | CAB=Je-Euy0Em+nMVixhJy6Ku2K3CiADZ_EfGt2FA_jfKmmgwDg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers pgsql-jdbc |
>Is it a bug or do we have other any alternate way to handle this ?
PostgreSQL is strongly against "partial commits to the database". If
you think a bit about it, it is not that bad.
You got an error, what is the business case to commit the partial
transaction then?
Exceptions should not be used for a "control flow", should they?
If you want to shoot yourself in a foot for fun and profit, you can
try https://github.com/pgjdbc/pgjdbc/pull/477.
What it does, it creates savepoints before each statement, then it
rollbacks to that savepoint in case of failure.
Vladimir
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Victor Blomqvist | 2016-02-18 08:17:03 | Query plan not updated after dropped index |
| Previous Message | Sridhar N Bamandlapally | 2016-02-18 07:59:45 | Re: JDBC behaviour |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2016-02-18 08:13:43 | Re: pg_ctl promote wait |
| Previous Message | Sridhar N Bamandlapally | 2016-02-18 07:59:45 | Re: JDBC behaviour |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sridhar N Bamandlapally | 2016-02-18 08:26:59 | Re: JDBC behaviour |
| Previous Message | Sridhar N Bamandlapally | 2016-02-18 07:59:45 | Re: JDBC behaviour |