You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's needed to have ability to modify(create|remove|update) some objects on another object modification. So modifications should be made in one transaction to be sure that everything is modificated or nothing. If cascade operation is failed then transaction must be roll backed and original exception must be thown. For example, on user removing we should remove all his workspaces. If it's not allowed to remove workspace then REST API Client should get original exception like -> 409 "Running workspace can't be removed"
The text was updated successfully, but these errors were encountered:
sleshchenko
added
status/code-review
This issue has a pull request posted for it and is awaiting code review completion by the community.
and removed
status/in-progress
This issue has been taken by an engineer and is under active development.
labels
Dec 22, 2016
It's needed to have ability to modify(create|remove|update) some objects on another object modification. So modifications should be made in one transaction to be sure that everything is modificated or nothing. If cascade operation is failed then transaction must be roll backed and original exception must be thown. For example, on user removing we should remove all his workspaces. If it's not allowed to remove workspace then REST API Client should get original exception like -> 409 "Running workspace can't be removed"
The text was updated successfully, but these errors were encountered: