Very odd. Please file a Jira. Maybe we can reproduce it with our unit tests? So
what is optimistically locked in this case?
Andrus
On Nov 5, 2010, at 9:30 AM, Michael Gentry wrote:
> It even fails if I include the dependent:
>
>
> DataContext dataContext = DataContext.createDataContext();
>
> User admin = dataContext.newObject(User.class);
>
> admin.setName("Administrator");
> admin.setUsername("admin");
>
> Avatar avatar = dataContext.newObject(Avatar.class);
> admin.setAvatar(avatar);
>
> dataContext.commitChanges();
>
> admin.setName("The Administrator");
>
> dataContext.commitChanges();
>
>
> Same issue. Both records get inserted this time (ID = 200). Then on
> the second commit the ID goes to null in the master (User) record.
>
> mrg
>
