Bug #11840
closed
[API] [Workbench] unique constraint violation error on index_collections_on_owner_uuid_and_name when untrashing a trashed collection
Description
I deleted a collection in my home project.
Then renamed another collection to have the same name as the deleted collection.
After that, I went to /trash page, and tried to untrash the first collection.
The collection was not untrashed, but no error message was shown either.
Looking at the workbench log, I see that the unique constraint violation took place.
Updated by Tom Clegg over 7 years ago
add the "ensure_unique_name" feature to the "update" method (currently it is only available in "create").
Now that we also have a separate "untrash" API, we'd also need to add the "ensure_unique_name" feature there too.
Presumably Workbench would always set the ensure_unique_name flag when calling untrash.
Updated by Radhika Chippada over 7 years ago
- Subject changed from [Workbench] unique constraint violation error on index_collections_on_owner_uuid_and_name when untrashing a trashed collection to [API] [Workbench] unique constraint violation error on index_collections_on_owner_uuid_and_name when untrashing a trashed collection
Updated by Radhika Chippada over 7 years ago
- Assigned To set to Radhika Chippada
- Target version set to 2017-07-05 sprint
Updated by Radhika Chippada over 7 years ago
- Status changed from New to In Progress
Updated by Radhika Chippada over 7 years ago
Branch 11840-unique-constraint-untrash-coll @ 7415bc3f7239b5c062e3876681265912d8150edd
Test run @ https://ci.curoverse.com/job/developer-run-tests/349/
Updated by Peter Amstutz over 7 years ago
Updated by Radhika Chippada over 7 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Applied in changeset arvados|commit:69e9a3e41a8d381adc095718a73a8a99a7943a5a.