[slindsey]

Just to take a different perspective for anyone reading this, your database is more than _just_ your persistence layer. It can be where rules about the business live. Rather than rely on 12 different applications or code in 27 different files to maintain the proper rules, you can enforce those rules right where the data lives, guaranteeing that no matter what moron is writing code, the data will be pristine because the database has checked it before putting it in.

Edit: Just to be clear, I'm not saying it's the right thing to do, at least not in every case. But it's an option; one that's different from the parent's perspective anyhow.

[turtleyacht]

Interesting. Mutation testing on database tables. Instead of testing application code, business rules--and constraints--are mutated against a test suite--

Most databases probably don't have test suites. But, it would be interesting to see if any work has been done on mutating constraints or "dirty data" injection.

This would ideally take the form of some annotated algebra, so that it is db driver agnostic, if possible.