>>
>> 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
> - load using an inner join
>
ok, log as WARN
> 2) @OneToOne is annotated with @NotFound(IGNORE)
> - throw an exception saying that @NotFound(IGNORE) is not allowed with
> derived IDs
>
ok, log as WARN
> What do you think?
>
> Gail
mmanuel Bernard"
To: hibernate-dev@lists.jboss.org
Sent: Wednesday, August 24, 2011 12:08:33 PM
Subject: [hibernate-dev] On @OneToOne(optional=true) and
@PrimaryKeyJoinColumn
There is a distinction between optional=true and @NotFound
I have had a few discussions with Gail on
https://
There is a distinction between optional=true and @NotFound
I have had a few discussions with Gail on
https://hibernate.onjira.com/browse/HHH-4982 and
https://hibernate.onjira.com/browse/ANN-725
Don't spend too much time on these issue reports, they are very confusing.
The question boils down to
