-
Notifications
You must be signed in to change notification settings - Fork 492
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API: Cleaner messaging when attempting to delete a user that has "history" #2825
Comments
One is unable to delete a user with a published dataset either: #2824 (comment) |
This is the desired behavior, as we want to track ho did what. However, we should make the API call cleaner, I think, by checking for these things first and providing a friendlier message. |
In DVN 3.6 we don't delete users, we deactivate their accounts when necessary. It doesn't seem to be possible though: #2419 |
Yep. We haven't forgotten about that issue ( @scolapasta and I discussed it last week at #2824 (comment) and below) but thanks for linking it here, @bencomp |
This issue may be a duplicate of #1929. |
Combined with #1929 |
Related to #2824 about deleting users, it's impossible to delete a user if that user had published the root dataverse:
org.postgresql.util.PSQLException: ERROR: update or delete on table "authenticateduser" violates foreign key constraint "fk_dvobject_releaseuser_id" on table "dvobject"
Detail: Key (id)=(8) is still referenced from table "dvobject".
I'm not sure what the right fix for this should be. Would we change the "releaseuser" for the root dataverse to some other existing user?
The text was updated successfully, but these errors were encountered: