> Your compiler doesn’t — and can’t — know what’s in your database. At compile time, yes it can. Not inherently the compiler itself, but at compile time the pr

> Your compiler doesn’t — and can’t — know what’s in your database. At compile time, yes it can. Not inherently the compiler itself, but at compile time the process can fail to build if your models do not match the schema in the DB. Diesel, for example, keeps the schema in code and (optionally) compares it to that of the DB. Ensuring that at compile to your code matches the schema of the DB. That of course doesn't handle changes to the schema post-build, but I hope no one is ad-hoc modifying their DB :) edit: And this becomes even more of a local, isolated solution if your ORM is also managing your migrations. Which, in the case of Diesel, it also (optionally) does.