---
title: "Comment by QRiQRa Team on \"PostgreSQL: A Practical Guide to the Database Engineers Agree On\" | Hashnode"
description: "The section on letting the database enforce the rules, not only the application, is a useful starting point. A NOT NULL, a foreign key, or a CHECK constraint wi"
url: "https://hashnode.com/posts/postgresql-practical-guide/6af7eb508797a7997b8a75e0/comment/6af84c941afc6c818c63d851"
---

[Discussion](https://hashnode.com/posts/postgresql-practical-guide/6af7eb508797a7997b8a75e0)

Comment [PostgreSQL: A Practical Guide to the Database Engineers Agree On](https://hashnode.com/posts/postgresql-practical-guide/6af7eb508797a7997b8a75e0)

[QRiQRa Team](https://hashnode.com/@qriqra)

[1d ago](https://hashnode.com/posts/postgresql-practical-guide/6af7eb508797a7997b8a75e0/comment/6af84c941afc6c818c63d851)

The section on letting the database enforce the rules, not only the application, is a useful starting point. A NOT NULL, a foreign key, or a CHECK constraint will still apply when a new path writes to the same table. I also appreciated the habit of proving a backup actually restores, rather than only confirming that a backup job ran. The "where it does not fit" part is just as valuable as the praise. Knowing when to pick something else keeps this from being a one-tool answer.
