At the moment I don't know if.connections are opened in transaction mode. Must I use this mode? With XA driver I can't use connection.commit. I use only stored function in SQL or pgsql language.
Thanks.
Mephysto
Il giorno 09/mag/2012 21:21, "Dave Cramer" <pg@fastcrypt.com> 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 ?
On Wed, May 9, 2012 at 3:11 PM, mephysto <mephystoonhell@gmail.com> 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 can't 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 can't know the wait state of user1 and I > can't take back he to his request. > Moreover, if transaction lock my table, and other user, user3, send a > message to user4, I can't 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 > Sent from the PostgreSQL - jdbc mailing list archive at Nabble.com. > > -- > Sent via pgsql-jdbc mailing list (pgsql-jdbc@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-jdbc