-Original Message-----
> > From: hibernate-dev-boun...@lists.jboss.org [mailto:hibernate-dev-
> boun...@lists.jboss.org]
> > On Behalf Of Jason Pyeron
> > Sent: Monday, April 20, 2020 1:12 AM
> > To: hibernate-us...@lists.jboss.org; hibernate-dev@lists.j
nday, April 20, 2020 1:12 AM
> To: hibernate-us...@lists.jboss.org; hibernate-dev@lists.jboss.org
> Subject: Re: [hibernate-dev] HHH-13959 - OneToOne JoinTable with unique
> constraints work
> around?
>
> [pardon the top post, it did not mix in well]
>
> It looks like [stack trace 1] t
> On Behalf Of Jason Pyeron
> Sent: Sunday, April 19, 2020 11:18 PM
> To: hibernate-us...@lists.jboss.org; hibernate-dev@lists.jboss.org
> Subject: [hibernate-dev] HHH-13959 - OneToOne JoinTable with unique
> constraints work
> around?
>
> https://hibernate.atlassian.net/b
https://hibernate.atlassian.net/browse/HHH-13959
I started a DB migration today, now we are dead in the water due to this
exception.
When I persist an Entity on the owning side of the OneToOne(optional=true)
relationship, and that property is null we are getting:
