haha I can see why we disagree. Same problems, different solutions. Often there are dozens of applications (or independent modules) using the database

haha I can see why we disagree. Same problems, different solutions. Often there are dozens of applications (or independent modules) using the database I know! I always assume that someone will try to pull this on me, some shortsighted bugger always does, and I end up on crusde protecting my platform against this! It is fundamentally bad design to have more than one application dependent on a database, and you're right, it's used everywhere. If I do a PhD one day, it will be on this topic. It's the number one stupid design in enterprise computing. I've spent years trying to write a logic framework to surround schemas to make it possible to do the functionality of pl/sql, but with stateful sessions. Every eighteen months I have a new go at it and rewrite. I have the ideas working, and use the patterns now, but haven't managed to create a framework of it that would be usable to anyone else. Anyway, the discussion on "all logic in DB" vs "all logic in the app" is part of the neverending struggle between DBAs and app programmers... Yeah. When I was doing a lot of relational work, I'd enforce these checks by having business logic layers around my ORM.