8:16 a.m.
Support use of Envers with Auto-commit mode.
--------------------------------------------
Key: HHH-4555
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4555
Project: Hibernate Core
Issue Type: New Feature
Components: envers
Affects Versions: 3.5.0-Beta-2
Environment: Hibernate 3.5.0-Beta-2
Reporter: Kevin Schmidt
Currently Envers is designed so that it synchronizes with the currently running
transaction in order to know when to commit the inserts into the Audit Tables. This is an
effective strategy for ensuring that the audit information is only saved to the database
if the Transactional Unit of Work which caused the audit data to be created is committed.
This design creates a limitation on Envers such that it cannot persist audit
information unless there is an active transaction. This effectively disables auditing for
anyone modifying data using Hibernate outside of a Hibernate Transaction. Specifically,
if you are using Autocommit = True and manually flushing the Hibernate Session then you
cannot have any of your data audited using Envers.
I am not that well versed with the design of Envers but was hoping this situation
could be detected and avoided. Maybe the audit information could be synchronized on the
flush event rather than when a transaction is committed to the database.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:16 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-4555) Support use of Envers with Auto-commit mode.
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4555?page=c...
]
Kevin Schmidt commented on HHH-4555:
------------------------------------
I might be able to take a stab at making a patch with some guidance on the design of a
feature like this.
Support use of Envers with Auto-commit mode.
--------------------------------------------
Key: HHH-4555
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4555
Project: Hibernate Core
Issue Type: New Feature
Components: envers
Affects Versions: 3.5.0-Beta-2
Environment: Hibernate 3.5.0-Beta-2
Reporter: Kevin Schmidt
Currently Envers is designed so that it synchronizes with the currently running
transaction in order to know when to commit the inserts into the Audit Tables. This is an
effective strategy for ensuring that the audit information is only saved to the database
if the Transactional Unit of Work which caused the audit data to be created is committed.
This design creates a limitation on Envers such that it cannot persist audit
information unless there is an active transaction. This effectively disables auditing for
anyone modifying data using Hibernate outside of a Hibernate Transaction. Specifically,
if you are using Autocommit = True and manually flushing the Hibernate Session then you
cannot have any of your data audited using Envers.
I am not that well versed with the design of Envers but was hoping this situation
could be detected and avoided. Maybe the audit information could be synchronized on the
flush event rather than when a transaction is committed to the database.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:33 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-4555) Support use of Envers with Auto-commit mode.
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4555?page=c...
]
Steve Ebersole commented on HHH-4555:
-------------------------------------
autocommit is evil and I am very -1 on changes to specifically support it.
Support use of Envers with Auto-commit mode.
--------------------------------------------
Key: HHH-4555
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4555
Project: Hibernate Core
Issue Type: New Feature
Components: envers
Affects Versions: 3.5.0-Beta-2
Environment: Hibernate 3.5.0-Beta-2
Reporter: Kevin Schmidt
Currently Envers is designed so that it synchronizes with the currently running
transaction in order to know when to commit the inserts into the Audit Tables. This is an
effective strategy for ensuring that the audit information is only saved to the database
if the Transactional Unit of Work which caused the audit data to be created is committed.
This design creates a limitation on Envers such that it cannot persist audit
information unless there is an active transaction. This effectively disables auditing for
anyone modifying data using Hibernate outside of a Hibernate Transaction. Specifically,
if you are using Autocommit = True and manually flushing the Hibernate Session then you
cannot have any of your data audited using Envers.
I am not that well versed with the design of Envers but was hoping this situation
could be detected and avoided. Maybe the audit information could be synchronized on the
flush event rather than when a transaction is committed to the database.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:35 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-4555) Support use of Envers with Auto-commit mode.
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4555?page=c...
]
Steve Ebersole commented on HHH-4555:
-------------------------------------
And btw, pretty sure you do not need to be using the Hibernate Transaction API; pretty
sure this would integrate with JTA as well. But Adam would know that aspect better.
Support use of Envers with Auto-commit mode.
--------------------------------------------
Key: HHH-4555
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4555
Project: Hibernate Core
Issue Type: New Feature
Components: envers
Affects Versions: 3.5.0-Beta-2
Environment: Hibernate 3.5.0-Beta-2
Reporter: Kevin Schmidt
Currently Envers is designed so that it synchronizes with the currently running
transaction in order to know when to commit the inserts into the Audit Tables. This is an
effective strategy for ensuring that the audit information is only saved to the database
if the Transactional Unit of Work which caused the audit data to be created is committed.
This design creates a limitation on Envers such that it cannot persist audit
information unless there is an active transaction. This effectively disables auditing for
anyone modifying data using Hibernate outside of a Hibernate Transaction. Specifically,
if you are using Autocommit = True and manually flushing the Hibernate Session then you
cannot have any of your data audited using Envers.
I am not that well versed with the design of Envers but was hoping this situation
could be detected and avoided. Maybe the audit information could be synchronized on the
flush event rather than when a transaction is committed to the database.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:35 a.m.
New subject: [Hibernate-JIRA] Assigned: (HHH-4555) Support use of Envers with Auto-commit mode.
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4555?page=c...
]
Steve Ebersole reassigned HHH-4555:
-----------------------------------
Assignee: Adam Warski
Support use of Envers with Auto-commit mode.
--------------------------------------------
Key: HHH-4555
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4555
Project: Hibernate Core
Issue Type: New Feature
Components: envers
Affects Versions: 3.5.0-Beta-2
Environment: Hibernate 3.5.0-Beta-2
Reporter: Kevin Schmidt
Assignee: Adam Warski
Currently Envers is designed so that it synchronizes with the currently running
transaction in order to know when to commit the inserts into the Audit Tables. This is an
effective strategy for ensuring that the audit information is only saved to the database
if the Transactional Unit of Work which caused the audit data to be created is committed.
This design creates a limitation on Envers such that it cannot persist audit
information unless there is an active transaction. This effectively disables auditing for
anyone modifying data using Hibernate outside of a Hibernate Transaction. Specifically,
if you are using Autocommit = True and manually flushing the Hibernate Session then you
cannot have any of your data audited using Envers.
I am not that well versed with the design of Envers but was hoping this situation
could be detected and avoided. Maybe the audit information could be synchronized on the
flush event rather than when a transaction is committed to the database.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:05 a.m.
New subject: [Hibernate-JIRA] Issue Comment Edited: (HHH-4555) Support use of Envers with Auto-commit mode.
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4555?page=c...
]
Paul Poole edited comment on HHH-4555 at 1/18/12 9:03 AM:
----------------------------------------------------------
Steve, there are other reasons to support this request than autocommit. We have a need to
more tightly control the flushing, so we use manual flush, but we do NOT use auto-commit,
which I agree is evil. Will you be supporting this feature at any time in the future?
was (Author: pppoole):
Steve, there are other reasons to support this request than autocommit. We have a
need to more tightly control the flushing, so we use manual flush, but we do NOT use
auto-commit, which I agree is evil. Will you be supporting that feature at any time in
the future?
Support use of Envers with Auto-commit mode.
--------------------------------------------
Key: HHH-4555
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4555
Project: Hibernate ORM
Issue Type: New Feature
Components: envers
Affects Versions: 3.5.0-Beta-2
Environment: Hibernate 3.5.0-Beta-2
Reporter: Kevin Schmidt
Assignee: Adam Warski
Currently Envers is designed so that it synchronizes with the currently running
transaction in order to know when to commit the inserts into the Audit Tables. This is an
effective strategy for ensuring that the audit information is only saved to the database
if the Transactional Unit of Work which caused the audit data to be created is committed.
This design creates a limitation on Envers such that it cannot persist audit
information unless there is an active transaction. This effectively disables auditing for
anyone modifying data using Hibernate outside of a Hibernate Transaction. Specifically,
if you are using Autocommit = True and manually flushing the Hibernate Session then you
cannot have any of your data audited using Envers.
I am not that well versed with the design of Envers but was hoping this situation
could be detected and avoided. Maybe the audit information could be synchronized on the
flush event rather than when a transaction is committed to the database.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:05 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-4555) Support use of Envers with Auto-commit mode.
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4555?page=c...
]
Paul Poole commented on HHH-4555:
---------------------------------
Steve, there are other reasons to support this request than autocommit. We have a need to
more tightly control the flushing, so we use manual flush, but we do NOT use auto-commit,
which I agree is evil. Will you be supporting that feature at any time in the future?
Support use of Envers with Auto-commit mode.
--------------------------------------------
Key: HHH-4555
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4555
Project: Hibernate ORM
Issue Type: New Feature
Components: envers
Affects Versions: 3.5.0-Beta-2
Environment: Hibernate 3.5.0-Beta-2
Reporter: Kevin Schmidt
Assignee: Adam Warski
Currently Envers is designed so that it synchronizes with the currently running
transaction in order to know when to commit the inserts into the Audit Tables. This is an
effective strategy for ensuring that the audit information is only saved to the database
if the Transactional Unit of Work which caused the audit data to be created is committed.
This design creates a limitation on Envers such that it cannot persist audit
information unless there is an active transaction. This effectively disables auditing for
anyone modifying data using Hibernate outside of a Hibernate Transaction. Specifically,
if you are using Autocommit = True and manually flushing the Hibernate Session then you
cannot have any of your data audited using Envers.
I am not that well versed with the design of Envers but was hoping this situation
could be detected and avoided. Maybe the audit information could be synchronized on the
flush event rather than when a transaction is committed to the database.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:06 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-4555) Support use of Envers with Auto-commit mode.
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4555?page=c...
]
Steve Ebersole commented on HHH-4555:
-------------------------------------
Paul, I have no idea what you mean. Can you clarify? If you mean that you need to/want
to flush before transaction times, just call flush()
Support use of Envers with Auto-commit mode.
--------------------------------------------
Key: HHH-4555
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4555
Project: Hibernate ORM
Issue Type: New Feature
Components: envers
Affects Versions: 3.5.0-Beta-2
Environment: Hibernate 3.5.0-Beta-2
Reporter: Kevin Schmidt
Assignee: Adam Warski
Currently Envers is designed so that it synchronizes with the currently running
transaction in order to know when to commit the inserts into the Audit Tables. This is an
effective strategy for ensuring that the audit information is only saved to the database
if the Transactional Unit of Work which caused the audit data to be created is committed.
This design creates a limitation on Envers such that it cannot persist audit
information unless there is an active transaction. This effectively disables auditing for
anyone modifying data using Hibernate outside of a Hibernate Transaction. Specifically,
if you are using Autocommit = True and manually flushing the Hibernate Session then you
cannot have any of your data audited using Envers.
I am not that well versed with the design of Envers but was hoping this situation
could be detected and avoided. Maybe the audit information could be synchronized on the
flush event rather than when a transaction is committed to the database.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:38 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-4555) Support use of Envers with Auto-commit mode.
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4555?page=c...
]
Paul Poole commented on HHH-4555:
---------------------------------
Steve, I could be incorrect as I am operating on an analysis done by a colleague. But, I
am under the impression that the Flush mode must be set to transaction. In our
application, we have the flush mode set to manual so that we can better control the
flushing. Worth noting, the analysis was done on a 1.2.x (not sure of the exact number)
version of Envers as we are currently on hibernate 3.3.x. If this is incorrect, then I
apologize and will discuss this with my colleague. Thanks!
Support use of Envers with Auto-commit mode.
--------------------------------------------
Key: HHH-4555
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4555
Project: Hibernate ORM
Issue Type: New Feature
Components: envers
Affects Versions: 3.5.0-Beta-2
Environment: Hibernate 3.5.0-Beta-2
Reporter: Kevin Schmidt
Assignee: Adam Warski
Currently Envers is designed so that it synchronizes with the currently running
transaction in order to know when to commit the inserts into the Audit Tables. This is an
effective strategy for ensuring that the audit information is only saved to the database
if the Transactional Unit of Work which caused the audit data to be created is committed.
This design creates a limitation on Envers such that it cannot persist audit
information unless there is an active transaction. This effectively disables auditing for
anyone modifying data using Hibernate outside of a Hibernate Transaction. Specifically,
if you are using Autocommit = True and manually flushing the Hibernate Session then you
cannot have any of your data audited using Envers.
I am not that well versed with the design of Envers but was hoping this situation
could be detected and avoided. Maybe the audit information could be synchronized on the
flush event rather than when a transaction is committed to the database.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:53 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-4555) Support use of Envers with Auto-commit mode.
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4555?page=c...
]
Steve Ebersole commented on HHH-4555:
-------------------------------------
Paul, "the Flush mode must be set to transaction" according to what/whom? Did
you try?
Adam?
Support use of Envers with Auto-commit mode.
--------------------------------------------
Key: HHH-4555
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4555
Project: Hibernate ORM
Issue Type: New Feature
Components: envers
Affects Versions: 3.5.0-Beta-2
Environment: Hibernate 3.5.0-Beta-2
Reporter: Kevin Schmidt
Assignee: Adam Warski
Currently Envers is designed so that it synchronizes with the currently running
transaction in order to know when to commit the inserts into the Audit Tables. This is an
effective strategy for ensuring that the audit information is only saved to the database
if the Transactional Unit of Work which caused the audit data to be created is committed.
This design creates a limitation on Envers such that it cannot persist audit
information unless there is an active transaction. This effectively disables auditing for
anyone modifying data using Hibernate outside of a Hibernate Transaction. Specifically,
if you are using Autocommit = True and manually flushing the Hibernate Session then you
cannot have any of your data audited using Envers.
I am not that well versed with the design of Envers but was hoping this situation
could be detected and avoided. Maybe the audit information could be synchronized on the
flush event rather than when a transaction is committed to the database.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:51 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-4555) Support use of Envers with Auto-commit mode.
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4555?page=c...
]
Paul Poole commented on HHH-4555:
---------------------------------
Steve, according to my colleague, he tried running with flush mode set to Manual and our
tests passed, but nothing was audited by Envers. He tried additional flush modes, but had
failures (the latter failures are more than likely a problem with how our system is
architected - not sure why manual didn't work). If there is no know restriction, I
will look into this myself more thoroughly and if I find an issue (with a newer release),
then I will create an issue. Hopefully Adam will confirm that manual is OK - if it is, it
could be some type of setup problem. Thanks.
Support use of Envers with Auto-commit mode.
--------------------------------------------
Key: HHH-4555
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4555
Project: Hibernate ORM
Issue Type: New Feature
Components: envers
Affects Versions: 3.5.0-Beta-2
Environment: Hibernate 3.5.0-Beta-2
Reporter: Kevin Schmidt
Assignee: Adam Warski
Currently Envers is designed so that it synchronizes with the currently running
transaction in order to know when to commit the inserts into the Audit Tables. This is an
effective strategy for ensuring that the audit information is only saved to the database
if the Transactional Unit of Work which caused the audit data to be created is committed.
This design creates a limitation on Envers such that it cannot persist audit
information unless there is an active transaction. This effectively disables auditing for
anyone modifying data using Hibernate outside of a Hibernate Transaction. Specifically,
if you are using Autocommit = True and manually flushing the Hibernate Session then you
cannot have any of your data audited using Envers.
I am not that well versed with the design of Envers but was hoping this situation
could be detected and avoided. Maybe the audit information could be synchronized on the
flush event rather than when a transaction is committed to the database.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:08 a.m.
New subject: [Hibernate-JIRA] Closed: (HHH-4555) Support use of Envers with Auto-commit mode.
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4555?page=c...
]
Steve Ebersole closed HHH-4555.
-------------------------------
Resolution: Rejected
I think a new issue is more appropriate. This issue specifically asks for supporting
auto-commit which I am definitely against. Try it and if you have problems using
FlushMode.MANUAL with 4.0 open an appropriate new issue. Really its up to Adam to
determine if that would be a bug or RFE
Support use of Envers with Auto-commit mode.
--------------------------------------------
Key: HHH-4555
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4555
Project: Hibernate ORM
Issue Type: New Feature
Components: envers
Affects Versions: 3.5.0-Beta-2
Environment: Hibernate 3.5.0-Beta-2
Reporter: Kevin Schmidt
Assignee: Adam Warski
Currently Envers is designed so that it synchronizes with the currently running
transaction in order to know when to commit the inserts into the Audit Tables. This is an
effective strategy for ensuring that the audit information is only saved to the database
if the Transactional Unit of Work which caused the audit data to be created is committed.
This design creates a limitation on Envers such that it cannot persist audit
information unless there is an active transaction. This effectively disables auditing for
anyone modifying data using Hibernate outside of a Hibernate Transaction. Specifically,
if you are using Autocommit = True and manually flushing the Hibernate Session then you
cannot have any of your data audited using Envers.
I am not that well versed with the design of Envers but was hoping this situation
could be detected and avoided. Maybe the audit information could be synchronized on the
flush event rather than when a transaction is committed to the database.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4549
days inactive
5350
days old
hibernate-issues@lists.jboss.org
11 comments
3 participants
participants (3)
-
Kevin Schmidt (JIRA) -
Paul Poole (JIRA)
-
Steve Ebersole (JIRA)