Re: [HACKERS] Statement-level rollback
| От | legrand legrand |
|---|---|
| Тема | Re: [HACKERS] Statement-level rollback |
| Дата | |
| Msg-id | DB5PR03MB1029B8E6B9841C6672938778902E0@DB5PR03MB1029.eurprd03.prod.outlook.com обсуждение исходный текст |
| Ответ на | Re: [HACKERS] Statement-level rollback (Vladimir Sitnikov <sitnikov.vladimir@gmail.com>) |
| Список | pgsql-hackers |
There was a mistake in my driver definition,
this works fine with autosave=always (but not with autoSave ...)
Thanks Again
De : Vladimir Sitnikov [via PostgreSQL] <ml-node+[hidden email]>
Envoyé : mardi 7 mars 2017 22:32:27
À : legrand legrand
Objet : Re: Statement-level rollback
Envoyé : mardi 7 mars 2017 22:32:27
À : legrand legrand
Objet : Re: Statement-level rollback
Please disregard my previous message.
pgjdbc is already doing upcase conversion, so I would like to see a test case that reproduces the error.
Alternatively, could you please capture and share TRACE log? ( https://jdbc.postgresql.org/documentation/head/logging.html#configuration )
Vladimir
ср, 8 мар. 2017 г. в 1:26, Vladimir Sitnikov <[hidden email]>:
legrand>when usingversion 42.0.0 with
legrand> jdbc:postgresql://localhost:5432/postgres?autosave=always
The pitfall there is the value should be written with upper case like autosave=ALWAYS.
The pitfall there is the value should be written with upper case like autosave=ALWAYS.
I've filed https://github.com/pgjdbc/pgjdbc/issues/769 to improve that at some point.
Vladimir
If you reply to this email, your message will be added to the discussion below:
http://www.postgresql-archive.org/Statement-level-rollback-tp5946725p5948059.htmlView this message in context: RE: Statement-level rollback
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.
В списке pgsql-hackers по дате отправления: