Describe the bug
When updating an attribute for example with a client, the version in the client table should be updated as well.
This way it ensures that no-one else updated any other attribute in the meantime.
Version
17.0.0-SNAPSHOT
Expected behavior
Version number should be updated when an attribute changes
Actual behavior
No change in the version number, as the relation is owned by the "Many" side.
How to Reproduce?
- Enable JPA Map storage for clients
- Edit a client attribute like "Backchannel Logout Session Required"
- look at the client table and see if the version changes
Anything else?
This is been found when implementing #9645
Describe the bug
When updating an attribute for example with a client, the version in the client table should be updated as well.
This way it ensures that no-one else updated any other attribute in the meantime.
Version
17.0.0-SNAPSHOT
Expected behavior
Version number should be updated when an attribute changes
Actual behavior
No change in the version number, as the relation is owned by the "Many" side.
How to Reproduce?
Anything else?
This is been found when implementing #9645