Re: Fwd: Postgres JDBC, WS and commit

Поиск
Список
Период
Сортировка
От Radosław Smogura
Тема Re: Fwd: Postgres JDBC, WS and commit
Дата
Msg-id 9cec544c4e1685dd4ea0c67b9fa5a537@mail.softperience.eu
обсуждение исходный текст
Ответ на Re: Fwd: Postgres JDBC, WS and commit  (Mephysto <mephystoonhell@gmail.com>)
Ответы Re: Fwd: Postgres JDBC, WS and commit  (mephysto <mephystoonhell@gmail.com>)
Список pgsql-jdbc
Oh... yes. You need to use it. There is "Non Transactional Connection"
checkbox on Connection Pool, it should be disabled. When it's enabled,
connection will not be bound to transaction manager.

Regards,
Radek

On Wed, 9 May 2012 23:00:17 +0200, Mephysto wrote:
> At the moment I dont know if.connections are opened in transaction
> mode. Must I use this mode?
>  With XA driver I cant use connection.commit.
>  I use only stored function in SQL or pgsql language.
>
> Thanks.
>
> Mephysto
> Il giorno 09/mag/2012 21:21, "Dave Cramer"  ha scritto:
>
>> Even in a pool if you issue a commit then the data should be
>> committed. Is the connection open in transaction mode ? Are you
>> executing a commit ?
>>
>> Dave Cramer
>>
>> dave.cramer(at)credativ(dot)ca
>> http://www.credativ.ca [1]
>>
>> On Wed, May 9, 2012 at 3:11 PM, mephysto wrote:
>> > Hi Kevin,
>> > I will try to explain my scenario: with my application, many
>> users exchange
>> > message within them. User1 send message to user2 by a web
>> service. This web
>> > service send message and wait the response from user 2 before end
>> and send
>> > notice to user1. I cant know how many time is needed for
>> response, so, I
>> > would to save te state in a table on database to prevent
>> accidental
>> > disconnection of client from web service.
>> >
>> > But I found that, if transaction are not closed until web service
>> operation
>> > end, my table are not update, and I cant know the wait state of
>> user1 and I
>> > cant take back he to his request.
>> > Moreover, if transaction lock my table, and other user, user3,
>> send a
>> > message to user4, I cant save his state until user1 operation
>> end.
>> >
>> > Is it clear enough?
>> >
>> > Is there any wrong in my reasoning? Is there anything I ignore in
>> pool
>> > functionality?
>> >
>> > Thanks in advance.
>> >
>> > Mephysto
>> >
>> > --
>> > View this message in context:
>>
>
> http://postgresql.1045698.n5.nabble.com/Postgres-JDBC-WS-and-commit-tp5697657p5698263.html
>> [3]
>> > Sent from the PostgreSQL - jdbc mailing list archive at
>> Nabble.com.
>> >
>> > --
>> > Sent via pgsql-jdbc mailing list (pgsql-jdbc@postgresql.org [4])
>> > To make changes to your subscription:
>> > http://www.postgresql.org/mailpref/pgsql-jdbc [5]
>
>
> Links:
> ------
> [1] http://www.credativ.ca
> [2] mailto:mephystoonhell@gmail.com
> [3]
>
> http://postgresql.1045698.n5.nabble.com/Postgres-JDBC-WS-and-commit-tp5697657p5698263.html
> [4] mailto:pgsql-jdbc@postgresql.org
> [5] http://www.postgresql.org/mailpref/pgsql-jdbc
> [6] mailto:pg@fastcrypt.com


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

Предыдущее
От: Mephysto
Дата:
Сообщение: Re: Fwd: Postgres JDBC, WS and commit
Следующее
От: Mikko Tiihonen
Дата:
Сообщение: Patch: Add support for hstore extension - and map it to/from java.util.Map