Describe the bug
When creating a storage and renaming it, a revsion entity is created by envers. When a storage is assigned to a dataset, it is assigned to the most current revision entity. When the internal storage is changed, e.g. title, the dataset still points to the old revsion, so it keeps the old title, url, etc..
db screenshot:
frontend:
Is this a regression?
No.
Steps to Reproduce
Create an internal storage and go to step 5. Add a dataset to this storage. Then change the title of the storage in the admin UI. Go back to step 5 and notice that the title hasnt changed.
Expected behavior
The dataset should automatically be assigned to the latest storage revision entity.
Describe the bug When creating a storage and renaming it, a revsion entity is created by envers. When a storage is assigned to a dataset, it is assigned to the most current revision entity. When the internal storage is changed, e.g. title, the dataset still points to the old revsion, so it keeps the old title, url, etc..
db screenshot:
frontend:
Is this a regression? No.
Steps to Reproduce Create an internal storage and go to step 5. Add a dataset to this storage. Then change the title of the storage in the admin UI. Go back to step 5 and notice that the title hasnt changed.
Expected behavior The dataset should automatically be assigned to the latest storage revision entity.
Environment