[Hibernate-JIRA] Created: (HHH-6725) Bidirectional @OneToOne(optional=true) with a foreign ID generator should force optional=false
12:31 p.m.
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.0.next
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: http://www.atlassian.com/software/jira
12:33 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-6725) Bidirectional @OneToOne(optional=true) with a foreign ID generator should force optional=false
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6725?page=c...
]
Gail Badner commented on HHH-6725:
----------------------------------
Steve, I'm not sure if this should have priority set to Major. Feel free to downgrade
if you see fit.
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.0.next
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: http://www.atlassian.com/software/jira
11:57 a.m.
New subject: [Hibernate-JIRA] Updated: (HHH-6725) Bidirectional @OneToOne(optional=true) with a foreign ID generator should force optional=false
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6725?page=c...
]
Gail Badner updated HHH-6725:
-----------------------------
Fix Version/s: (was: 4.0.0.CR5)
4.0.0.next
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.0.next
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: http://www.atlassian.com/software/jira
7:47 p.m.
New subject: [Hibernate-JIRA] Updated: (HHH-6725) Bidirectional @OneToOne(optional=true) with a foreign ID generator should force optional=false
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6725?page=c...
]
Steve Ebersole updated HHH-6725:
--------------------------------
Fix Version/s: (was: 4.0.0.CR6)
4.0.0.next
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.0.next
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: http://www.atlassian.com/software/jira
6:23 a.m.
New subject: [Hibernate-JIRA] Updated: (HHH-6725) Bidirectional @OneToOne(optional=true) with a foreign ID generator should force optional=false
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6725?page=c...
]
Strong Liu updated HHH-6725:
----------------------------
Fix Version/s: (was: 4.0.0.CR7)
4.0.0.next
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.0.next
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: http://www.atlassian.com/software/jira
5:24 a.m.
New subject: [Hibernate-JIRA] Updated: (HHH-6725) Bidirectional @OneToOne(optional=true) with a foreign ID generator should force optional=false
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6725?page=c...
]
Steve Ebersole updated HHH-6725:
--------------------------------
Fix Version/s: (was: 4.0.0.Final)
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: http://www.atlassian.com/software/jira
11:51 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-6725) Bidirectional @OneToOne(optional=true) with a foreign ID generator should force optional=false
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6725?page=c...
]
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: http://www.atlassian.com/software/jira
9:27 a.m.
New subject: [Hibernate-JIRA] Updated: (HHH-6725) Bidirectional @OneToOne(optional=true) with a foreign ID generator should force optional=false
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6725?page=c...
]
Gail Badner updated HHH-6725:
-----------------------------
Fix Version/s: (was: 4.0.1)
4.1.0
No, it won't make it into 4.0.1. Hopefully, it will be easier to do with the new
metamodel.
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.1.0
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: http://www.atlassian.com/software/jira
1:45 p.m.
New subject: [Hibernate-JIRA] Commented: (HHH-6725) Bidirectional @OneToOne(optional=true) with a foreign ID generator should force optional=false
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6725?page=c...
]
Steve Ebersole commented on HHH-6725:
-------------------------------------
We can make sure it does! ;) Just let me know if there is any specific information you
need available and how.
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.1.0
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: http://www.atlassian.com/software/jira
8:23 a.m.
New subject: [Hibernate-JIRA] Commented: (HHH-6725) Bidirectional @OneToOne(optional=true) with a foreign ID generator should force optional=false
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6725?page=c...
]
Gail Badner commented on HHH-6725:
----------------------------------
Specifically, we need a way to check for a "foreign" ID generator with
@OneToOne(optional=true). In this case we want to log a warning and force optional=false.
It could be done while the persisters are being built, but I think it would be better if
this happens when the metadata is being built.
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.1.0
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: http://www.atlassian.com/software/jira
1 a.m.
New subject: [Hibernate-JIRA] Updated: (HHH-6725) Bidirectional @OneToOne(optional=true) with a foreign ID generator should force optional=false
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-6725?page=c...
]
Gail Badner updated HHH-6725:
-----------------------------
Fix Version/s: (was: 4.1.0)
5.0.0
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 ORM
Issue Type: Improvement
Reporter: Gail Badner
Assignee: Gail Badner
Fix For: 5.0.0
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: http://www.atlassian.com/software/jira
4753
days inactive
4854
days old
hibernate-issues@lists.jboss.org
10 comments
3 participants
participants (3)
-
Gail Badner (JIRA) -
Steve Ebersole (JIRA)
-
Strong Liu (JIRA)