Closed
Bug 671781
Opened 13 years ago
Closed 10 years ago
Delete users outright
Categories
(developer.mozilla.org Graveyard :: Wiki pages, defect, P3)
developer.mozilla.org Graveyard
Wiki pages
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: openjck, Unassigned)
References
Details
(Whiteboard: [type:feature])
No description provided.
Reporter | ||
Updated•13 years ago
|
Priority: -- → P2
Comment 1•12 years ago
|
||
Deleting a user object outright creates serious risk of DB integrity errors. A revision, for example, has a Foreign Key pointing to the Users table, identifying its author. (Actually, it has 2, one for its author and one for its approver). Deleting the user can quickly produce a FK cascade, if a user has created revisions that other revisions are based on, etc. And thanks to the Document.current_revision circular FK constraint, you can, in fact, end up deleting entire documents and all their history. Scrubbing all personalized data, including the profile, email address, password hash, etc, is safer. And the user's data is as effectively gone as if we'd deleted the table row completely, as those overwrites are non-recoverable.
Assignee | ||
Updated•12 years ago
|
Version: Kuma → unspecified
Assignee | ||
Updated•12 years ago
|
Component: Website → Landing pages
Comment 2•12 years ago
|
||
In the time since comment 1, I've spoken with Tom from Privacy about this. We have a set of recommendations that are sufficient, from their point of view. I'll dig them up and add them here when I can.
Updated•12 years ago
|
Whiteboard: u=administrator c=siteadmin p= → feature request; u=administrator c=siteadmin p=
Reporter | ||
Updated•11 years ago
|
Whiteboard: feature request; u=administrator c=siteadmin p= → [type:feature]
Reporter | ||
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
Updated•4 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•