So perfect for most web dev companies, then.

“We handle FKs in the app for flexibility.”

“And how many orphaned rows do you have?”

“…”

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.

	▲	sgarland 3 days ago \| parent \| next [-]
		> cannot express a whole application 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 3 days ago \| parent \| prev [-]
		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.