[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5187?page=c...
]
Emmanuel Bernard commented on HHH-5187:
---------------------------------------
For the sake of completeness, here are the reasons why we do not violate the spec:
- the specification does consider the lazy flag as optional "The
<code>LAZY</code> strategy is a hint to the persistence provider
runtime."
- We (the expert group) have added the sentence "The persistence provider must not
merge fields marked LAZY that have not been fetched: it must ignore such fields when
merging." to make sure that lazy fields (not necessarily associations) would not be
replaced by null but retain their database state. That was added after one three letter
acronym vendor was expecting the lazy state to be overridden by null.
Allow some control over whether or not an association is loaded via a
join on the merge path
--------------------------------------------------------------------------------------------
Key: HHH-5187
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5187
Project: Hibernate Core
Issue Type: New Feature
Components: core
Reporter: Emmanuel Bernard
--
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