Yeah, I think that is the author's point. That we shouldn't look to the application to enforce RI, etc, because who knows how long our software application will live...but the data will like outlive it.

>I (and perhaps many) do not always think in these terms. While I do have some stored procedures (e.g., RI, PK generator which is called by code placed in the default value of the PK field), I do not always follow strict DB modeling. Now if I were designing a DB where the front-end were unknow or variable, then I would dang sure build all the integrity constraints into the DB.