This has nothing to do with PostgreSQL specifically.
Please read up on Java (EE) application servers, connection pooling
and container transaction models.
Florent
On Mon, May 14, 2012 at 3:55 PM, mephysto <mephystoonhell@gmail.com> wrote:
> 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.
>
> --
> Sent via pgsql-jdbc mailing list (pgsql-jdbc@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-jdbc
--
Florent Guillaume, Director of R&D, Nuxeo
Open Source, Java EE based, Enterprise Content Management (ECM)
http://www.nuxeo.com http://www.nuxeo.org +33 1 40 33 79 87