Hacker News Reader

Why not just anonymize the data instead? Not using foreign key constraint just for the sake of GDPR sounds weird.

That and why not allow null for the foreign key constraint and set it to nullify upon deletion? Or indeed, anonymise data.

I have used that pattern in my apps and found it works well. But then I've watched video from respected DB experts, that I learn a great deal from, where they practically beg you to stop using nullable columns.

So I'm torn, because I think there may just be a major problem I've not yet grown my apps big enough to suffer. Anyone have thoughts either way?

Any particular videos you'd recommend?

> Not using foreign key constraint just for the sake of GDPR sounds weird.

That isn't what he said.

He said their inability to delete an account is due to poor design of their data schema by a well intentioned developer.

Reply on news.ycombinator.com