> Sure, it exists, but it would not be the ideal case. It is still not a sign that "you're doing it wrong". I prefer a single entry point to my data, too, but

> Sure, it exists, but it would not be the ideal case. It is still not a sign that "you're doing it wrong". I prefer a single entry point to my data, too, but I still want my databases to be consistent in the sense that schema-like details are not coded in the client-side. > Sure, there is some validation enforced by the DB in the relational case, but it is often not enough. Agreed. Why worry about the mere existence of important keys? This was never a debate whether all storage logic belongs to the database or not. The article argues to make your schema visible and keep your data easy to query.