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
Re: [JDBC] JDBC behaviour Re: JDBC behaviour |
Список | 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 по дате отправления: