>>
>> Maybe you're right but I don't have the same rightness feeling.
>>
>> Anyways, we can't rewrite history and we can differentiate not set
>> from set to a value in Java's annotations. Besides, I suspect (has to
>> be verified) that normal forms don't like null values even for foreign
>> key
Responses inline...
- Original Message -
> From: "Emmanuel Bernard"
> To: "Gail Badner"
> Cc: hibernate-dev@lists.jboss.org
> Sent: Wednesday, August 24, 2011 4:21:39 PM
> Subject: Re: [hibernate-dev] On @OneToOne(optional=true) and
> @PrimaryKey
On 24 août 2011, at 23:17, Gail Badner wrote:
> @NotFound is Hibernate-specific, isn't it? Is there anything in the JPA 2
> spec that covers this functionality?
Nope, JPA 2 does not cover this case.
>
> Since the default for @OneToOne is optional=true, it doesn't seem right that
> it always
@NotFound is Hibernate-specific, isn't it? Is there anything in the JPA 2 spec
that covers this functionality?
Since the default for @OneToOne is optional=true, it doesn't seem right that it
always be implicitly applied with @PrimaryKeyJoinColumn, unless optional=false
is explicitly specified.
