Re: [HACKERS] problem with new autocommit config parameter
| От | Barry Lind |
|---|---|
| Тема | Re: [HACKERS] problem with new autocommit config parameter |
| Дата | |
| Msg-id | 3D7A8032.4010706@xythos.com обсуждение исходный текст |
| Ответ на | Re: [HACKERS] problem with new autocommit config parameter and jdbc (Bruce Momjian <pgman@candle.pha.pa.us>) |
| Список | pgsql-jdbc |
Yes it is possible, but according to the jdbc spec, a new connection in jdbc is always initialized to autocommit=true. So jdbc needs to ignore whatever the current server setting is and reset to autocommit=true. --Barry snpe wrote: > On Saturday 07 September 2002 02:55 am, Bruce Momjian wrote: > >>Barry Lind wrote: >> >>>Haris, >>> >>>You can't use jdbc (and probably most other postgres clients) with >>>autocommit in postgresql.conf turned off. >>> >>>Hackers, >>> >>>How should client interfaces handle this new autocommit feature? Is it >>>best to just issue a set at the beginning of the connection to ensure >>>that it is always on? >> >>Yes, I thought that was the best fix for apps that can't deal with >>autocommit being off. > > Can client get information from backend for autocommit (on or off) and that > work like psql ? > > >
В списке pgsql-jdbc по дате отправления: