[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4493?page=c...
]
Emmanuel Bernard commented on HHH-4493:
---------------------------------------
Well i this case, you can't gracefully degrade. By "ignoring" one formula,
the non Hibernate provider will blow up claiming you have a FK / PK mismatch (for example
3 columns on the PK and only 2 properly declared on the FK - as the formula declaration is
"missing")
That being said, we need to see if the code change to AnnotationBinder and co is
disruptive or not. If not, we can add the feature as I said in the previous case, esp
since the declaration is more elegant.
Support FK formula using named reference and avoiding the
@JoinColumnOrFormula container
----------------------------------------------------------------------------------------
Key: HHH-4493
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4493
Project: Hibernate Core
Issue Type: Improvement
Components: annotations
Reporter: Emmanuel Bernard
Priority: Minor
First question, is it desirable? Does the benefit outweight the additional documentation
complexity (of two different approaches).
--
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