Re: [JDBC] JDBC behaviour

Поиск
Список
Период
Сортировка
От Vladimir Sitnikov
Тема Re: [JDBC] JDBC behaviour
Дата
Msg-id CAB=Je-Euy0Em+nMVixhJy6Ku2K3CiADZ_EfGt2FA_jfKmmgwDg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: JDBC behaviour  (Sridhar N Bamandlapally <sridhar.bn1@gmail.com>)
Ответы Re: [JDBC] JDBC behaviour  (Sridhar N Bamandlapally <sridhar.bn1@gmail.com>)
Re: [JDBC] JDBC behaviour  (Craig Ringer <craig@2ndquadrant.com>)
Re: JDBC behaviour  (Craig Ringer <craig@2ndquadrant.com>)
Список pgsql-general
>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


В списке pgsql-general по дате отправления:

Предыдущее
От: Sridhar N Bamandlapally
Дата:
Сообщение: Re: JDBC behaviour
Следующее
От: Victor Blomqvist
Дата:
Сообщение: Query plan not updated after dropped index