what version of tapestry is it ? there has been a recent fix that changes the way trasactions are handled. before that database connections were on autocommit and sometimes that caused the problems you describe. if you commit explicitely the problem will most likely be gone ...
Davor Hrg On Tue, Apr 22, 2008 at 5:26 PM, Moritz Gmelin <[EMAIL PROTECTED]> wrote: > Hi, > > There seems to be some threading issues when doing database updates from > page to page. > E.G. we have a page that displays a list of elements in a Database table > and a button that you can click to add a new entry. > The button is a ActionLink. Its method handler adds an element to the > database table and returns the user to the same page. > Normally, for each click of the button, I can see one row added to the > database and visible in the grid on the page. But sometimes if I click the > button, the content of the grid does not change although I can see that an > element was added to the database. > From other similar problems we have with the application, I would guess, > that the display of the new page happens with a new database session, where > the old session's transaction (to add the element) is not yet finished. > The environment we use is OS X with Java 1.5.0 and a PostgreSQL Database. > Has anybody else seen this behaviour? > Is there somewhere I can for a transaction to be completely finished > before the new page is activated ? > > Thanks > > Moritz > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
