Skip to content

Conversation

schauder
Copy link
Contributor

@schauder schauder commented Oct 1, 2018

The id-property was used to determine if there is an instance at all, or if it was null.
For entities that don't have an id that purpose is now fulfilled by selecting the backreference and checking it against null.

See also: DATAJDBC-223.

The id-property was used to determine if there is an instance at all, or if it was null.
For entities that don't have an id that purpose is now fulfilled by selecting the backreference and checking it against null.

See also: DATAJDBC-223.
@gregturn gregturn closed this Oct 10, 2018
@gregturn gregturn deleted the issue/DATAJDBC-266 branch October 10, 2018 14:58
@gregturn
Copy link
Contributor

Resolved via 0816f41.

mp911de pushed a commit that referenced this pull request Feb 21, 2022
mp911de pushed a commit that referenced this pull request Feb 21, 2022
Formatting.
Added issue to test comments.

Removed the test for presence of the id in case of a potential optimistic locking exception.
A deleted row is also a case of a concurrent modification and therefore should trigger the OptimisticLockingException.

Original pull request: #314.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants