[
https://issues.apache.org/jira/browse/TAPESTRY-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576736#action_12576736
]
Massimo Lusetti commented on TAPESTRY-2247:
-------------------------------------------
Well i probably don't get what you're referring to as "does more harm than
good" but having to explicitly call commit() on plain successfull unit of
operations seems a waste of time.
Please would you like to share some more thoughts?
Thanks
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
