> I don't think there's a recorded case of that ever happening with databases. > and there are other seams in your code which are much more likely to break. On

> I don't think there's a recorded case of that ever happening with databases. > and there are other seams in your code which are much more likely to break. One such thing is the abuse of layers and layers of abstractions. For example, many people (unfortunately, in my view) love to use ORMs and query builds, and things like these are much more easier to happen when things are too generic. And signing the entire database row and validating it, and so on, might be unjustified for most people, especially if you already count with correction from a TLS layer, and you can just have the trade-off of adding a simple conditional to check if the data you receive is sane. This is not something essential for everything, but that is nice to have, especially the further you're out of control. For example, if you retrieve data from an external API you should not trust it blindly, but rely on your internal references (security concerns aside, I'm talking about other kind of erratic behavior or bad data).