From: | mephysto <mephystoonhell(at)gmail(dot)com> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Fwd: Postgres JDBC, WS and commit |
Date: | 2012-05-14 13:55:25 |
Message-ID: | 1337003725711-5708644.post@n5.nabble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Excuse me but I'm really confused, I did many tests, but I'm not sure about
results. If I understand it, using glassfish JDBC connection pool, if a
thread requires a connection to database, glassfish assign one from pool to
thread and commit is executed at the end of thread, not on every stored
function launch.
I would, if it is possible, the commit is executed every write stored
function.
A this point, I would to know if this goal is achievable and if use of
commit that I wand is admissible. Finally, I would to know, why commit is
execute by deafult only one time at the end of thread.
Thanks in advance and excuse me newly.
Mephysto
--
View this message in context: http://postgresql.1045698.n5.nabble.com/Postgres-JDBC-WS-and-commit-tp5697657p5708644.html
Sent from the PostgreSQL - jdbc mailing list archive at Nabble.com.
From | Date | Subject | |
---|---|---|---|
Next Message | Florent Guillaume | 2012-05-14 14:16:24 | Re: Fwd: Postgres JDBC, WS and commit |
Previous Message | Radosław Smogura | 2012-05-14 10:26:58 | Re: Fwd: Postgres JDBC, WS and commit |