]
Steve Ebersole commented on HHH-6725:
-------------------------------------
TBH, I dont worry about priority overly much for numerous reasons. Howeverm you know how
I worry about versions :) Will you really be getting to this for 4.0.1?
Bidirectional @OneToOne(optional=true) with a foreign ID generator
should force optional=false
----------------------------------------------------------------------------------------------
Key: HHH-6725
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6725
Project: Hibernate Core
Issue Type: Improvement
Reporter: Gail Badner
Assignee: Gail Badner
Fix For: 4.0.1
When a foreign ID generator is used with @OneToOne(optional=true), Hibernate should:
- force optional=false
- log a warning
The default for @OneToOne is optional=true
This should be done when a foreign ID generator is used
- with @OneToOne @PrimaryKeyJoinColumn
- with @OneToOne(mappedBy="...")
Currently, Hibernate allows the one-to-one association to be optional, but if the
association is set to null, IdentifierGenerationException is thrown.
I don't think it's possible to check for a ForeignGenerator until the
SessionFactory or persister is being built with a Configuration object.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: