▲ 81 ▼ Is this cause for concern? Pretty sure I deleted this account long ago (lemmy.world) submitted 1 year ago by tudor@lemmy.world to c/privacy@lemmy.world 17 comments fedilink hide all child comments
[–] aeronmelon@lemmy.world 63 points 1 year ago (4 children) They just changed your username to DELETED? This would be funny if it wasn’t so concerning. permalink fedilink source hideshow 4 child comments replies: [–] HelloRoot@lemy.lol 10 points 1 year ago* There was recently a blog post (about acc deletion and gdpr) shared here where the company did exactly that and the blogwriter could even still log in. Will insert link later when I have time to dig it out. permalink fedilink source parent [–] devfuuu@lemmy.world 5 points 1 year ago* (2 children) So many places just do something like that, since the data itself rarely can be deleted easily. permalink fedilink source parent hideshow 2 child comments replies: [–] onslaught545@lemmy.zip 7 points 1 year ago (1 child) Any halfway competent DBA could delete it from live databases easily. Your account is going to have a unique identifier. It's usually done for compliance purposes regarding data retention. permalink fedilink source parent hideshow 1 child comment replies: [–] a4ng3l@lemmy.world 6 points 1 year ago Yeaaahhhh any competent DBA would be crucified for doing physical deletion nonchalantly in an actual corporate environment… Due to integrity issues within one database or across several ones in complex chains. Honestly a lots of the times logical deletion is preferred anyway. And then that deletion request would be propagated via events and then, maybe, possibly physically deleted. What’s the point in those over simplifications ? Makes dba looks lazy imho which isn’t a nice thing to do. permalink fedilink source parent
[–] HelloRoot@lemy.lol 10 points 1 year ago* There was recently a blog post (about acc deletion and gdpr) shared here where the company did exactly that and the blogwriter could even still log in. Will insert link later when I have time to dig it out. permalink fedilink source parent
[–] devfuuu@lemmy.world 5 points 1 year ago* (2 children) So many places just do something like that, since the data itself rarely can be deleted easily. permalink fedilink source parent hideshow 2 child comments replies: [–] onslaught545@lemmy.zip 7 points 1 year ago (1 child) Any halfway competent DBA could delete it from live databases easily. Your account is going to have a unique identifier. It's usually done for compliance purposes regarding data retention. permalink fedilink source parent hideshow 1 child comment replies: [–] a4ng3l@lemmy.world 6 points 1 year ago Yeaaahhhh any competent DBA would be crucified for doing physical deletion nonchalantly in an actual corporate environment… Due to integrity issues within one database or across several ones in complex chains. Honestly a lots of the times logical deletion is preferred anyway. And then that deletion request would be propagated via events and then, maybe, possibly physically deleted. What’s the point in those over simplifications ? Makes dba looks lazy imho which isn’t a nice thing to do. permalink fedilink source parent
[–] onslaught545@lemmy.zip 7 points 1 year ago (1 child) Any halfway competent DBA could delete it from live databases easily. Your account is going to have a unique identifier. It's usually done for compliance purposes regarding data retention. permalink fedilink source parent hideshow 1 child comment replies: [–] a4ng3l@lemmy.world 6 points 1 year ago Yeaaahhhh any competent DBA would be crucified for doing physical deletion nonchalantly in an actual corporate environment… Due to integrity issues within one database or across several ones in complex chains. Honestly a lots of the times logical deletion is preferred anyway. And then that deletion request would be propagated via events and then, maybe, possibly physically deleted. What’s the point in those over simplifications ? Makes dba looks lazy imho which isn’t a nice thing to do. permalink fedilink source parent
[–] a4ng3l@lemmy.world 6 points 1 year ago Yeaaahhhh any competent DBA would be crucified for doing physical deletion nonchalantly in an actual corporate environment… Due to integrity issues within one database or across several ones in complex chains. Honestly a lots of the times logical deletion is preferred anyway. And then that deletion request would be propagated via events and then, maybe, possibly physically deleted. What’s the point in those over simplifications ? Makes dba looks lazy imho which isn’t a nice thing to do. permalink fedilink source parent