top | item 45341590 (no title) rcrowley | 5 months ago The question isn't how many orphaned rows do you have, it's whether it matters. Databases are wonderful but they cannot maintain every invariant and they cannot express a whole application. They're one tool in the belt. discuss order hn newest sgarland|5 months ago > cannot express a whole applicationNot with that attitude: https://docs.postgrest.org/en/v13/index.htmlOrphaned rows can very much matter for data privacy concerns, which is also where I most frequently see this approach failing. jashmatthews|5 months ago Most companies can afford not to give a shit until they hit SOC2 or GDPR compliance and then suddenly orphaned data is a giant liability.
sgarland|5 months ago > cannot express a whole applicationNot with that attitude: https://docs.postgrest.org/en/v13/index.htmlOrphaned rows can very much matter for data privacy concerns, which is also where I most frequently see this approach failing.
jashmatthews|5 months ago Most companies can afford not to give a shit until they hit SOC2 or GDPR compliance and then suddenly orphaned data is a giant liability.
sgarland|5 months ago
Not with that attitude: https://docs.postgrest.org/en/v13/index.html
Orphaned rows can very much matter for data privacy concerns, which is also where I most frequently see this approach failing.
jashmatthews|5 months ago