[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2650?page=c...
]
Max Rydahl Andersen commented on HHH-2650:
------------------------------------------
if the patch is done properly and with good testcases then I would say it's fairly
high since it is a usefull construct.
Allow for an entire Session to be readOnly, add Session.setReadOnly()
method
----------------------------------------------------------------------------
Key: HHH-2650
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2650
Project: Hibernate3
Issue Type: Sub-task
Components: core
Environment: Any
Reporter: Gunther Schadow
Original Estimate: 1 day
Remaining Estimate: 1 day
There is a need for read-only applications to avoid any snapshoting of objects if that
application never intends to make updates. Such readOnly mode would be the mode in which
any object gets loaded into the session, whether directly or from lazy collections. The
use case is reporting applications which want to make sure that they don't even
accidentally make updates AND that want to save the time it takes to create snapshots
because they read through a lot of data very quickly. Our own need is that we have a rich
client where we hold read only sessions open for browsing and where we spawn off any
change transactions into separate Sessions. Even in change transactions we like to have
all objects locked from even accidental updates unless they are explicitly unlocked.
A Session.setReadOnly() method would be ideal to do this. It does not appear very hard to
make that improvement. We would do it ourselves even if we had some idea if (and under
which criteria) our modifications would have a chance to make it into future versions of
Hibernate?
--
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