Re: JDBC behaviour
| От | Sridhar N Bamandlapally |
|---|---|
| Тема | Re: JDBC behaviour |
| Дата | |
| Msg-id | CAGuFTBXf_1Vws=Ja3nCqvRGvWPE2W4ATpCyxrreCgWFi0Yii=w@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: JDBC behaviour (Andreas Joseph Krogh <andreas@visena.com>) |
| Ответы |
Re: JDBC behaviour
Re: JDBC behaviour |
| Список | pgsql-jdbc |
setAutoCommit(false), it should not be treating all next transactions as single set, simple, this is what expected behavior
On Thu, Feb 18, 2016 at 2:34 PM, Andreas Joseph Krogh <andreas@visena.com> wrote:
På torsdag 18. februar 2016 kl. 09:51:47, skrev Sridhar N Bamandlapally <sridhar.bn1@gmail.com>:Ok, let me put this wayin JDBC we have setAutoCommit( false ) , and all dmls are independent transactionsand when any transaction fails then the session not allowing next transactionsin Java when we do setAutoCommit( false ) its behaving like all transactions in BEGIN-END block, this is not expected behaviori guess this is bugNo, you got it backwards. With autocommit=false all statements are NOT independent transactions.--Andreas Joseph KroghCTO / Partner - Visena ASMobile: +47 909 56 963
Вложения
В списке pgsql-jdbc по дате отправления:
