tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Adams (JIRA)" <...@tapestry.apache.org>
Subject [jira] Assigned: (TAPESTRY-2247) Don't commit the transaction automatically at the end of the request
Date Sat, 08 Mar 2008 23:59:46 GMT

     [ https://issues.apache.org/jira/browse/TAPESTRY-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dan Adams reassigned TAPESTRY-2247:
-----------------------------------

    Assignee: Dan Adams

> Don't commit the transaction automatically at the end of the request
> --------------------------------------------------------------------
>
>                 Key: TAPESTRY-2247
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-2247
>             Project: Tapestry
>          Issue Type: Bug
>          Components: tapestry-hibernate
>    Affects Versions: 5.0.10
>            Reporter: Dan Adams
>            Assignee: Dan Adams
>
> On thread cleanup, the Session should be flushed not committed. If people want to commit
changes they should explicitly do so but having the transaction committed automatically can
lead to some very mysterious changing of the data. In my experience, having the transaction
committed automatically does more harm than good.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Mime
View raw message