[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-4493) Support FK formula using named reference and avoiding the @JoinColumnOrFormula container

[Paul Benedict (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34230#action_34230 ] 

Paul Benedict commented on HHH-4493:
------------------------------------

My reading was here: http://docs.sun.com/app/docs/doc/820-7627/bnbpy?a=view

My understanding of designing extensions is not to supplant (i.e., uproot) the uses of the standard. Thus, if it is valid to use @JoinColumn(s) today, it shouldn't have to be wrapped or replaced to extend the feature -- but allow additions on top. That's why I think this alternative is more fluent.

Also I think there is an argument here for portability. If entities do exist that are JPA compliant, but also take advantage of Hibernate features whenever Hibernate is the persistence provider, using a wrapper would hinder the possibility. I prefer a graceful degradation where possible.

> 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.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira