Re: [eclipselink-users] @ManyToOne(optional=false) versus @Column(nullab

[cowwoc <cowwoc@xxxxxxxxxxxxxxxx>]

Oops, I hit send too soon. The question should read:

I was under the impression that @ManyToOne(optional=false) will create
non-null columns, but it seems that it doesn't. Adding a
@JoinColumn(nullable=false) fixes the problem but then I'm left wondering
what optional=false is supposed to be doing...?

Is this a bug or a misunderstanding?

Thank you,
Gili


cowwoc wrote:
> 
> Hi,
> 
> I was under the impression that @ManyToOne(optional=false) versus
> @Column(nullable=false) will yield non-null columns, but it seems that
> @ManyToOne(optional=false) creates a nullable column.
> 
> Is this a bug or a misunderstanding?
> 
> Thank you,
> Gili
> 

-- 
View this message in context: http://www.nabble.com/%40ManyToOne%28optional%3Dfalse%29-versus-%40Column%28nullable%3Dfalse%29-tp20930371p20930395.html
Sent from the EclipseLink - Users mailing list archive at Nabble.com.