Re: Dreaming About Redesigning SQL
Date: 21 Oct 2003 12:10:49 GMT
Message-ID: <3505221.1066738677_at_dbforums.com>
Originally posted by Mike Preece
> Data integrity. Should it be the responsibility of the database
> management system or application code? "DMBS" I hear you cry. "It
> doesn't matter" I whisper. So long as it's maintained. You are writing
> some application code. You think you want to READ, WRITE & DELETE
> records - but you don't really. You want more. You only want to update
> the database if integrity is being maintained. Supposing there isn't
> any integrity checking happenning? Gee whiz. Bummer. I guess I'll have
> to use some standard function instead of doing a direct (raw) update.
> OK then. I will. Job done. Next!
Simple as that, eh? And if you are just one of 100 developers working on a project, your project management can just assume that you all do the right thing (use the standard function)? Or will every line of every programmer's code be subject to scrutiny by someone who infallibly spots EVERY single deviation from the business rules? Sure, that is an option. There may be 200 modules that have to write data to a core table. You can eyeball each one to ensure it does it correctly, or you can guarantee that they each do it correctly (or not at all) by ensuring that there is no possible way to bypass the rules. For a small database/application developed by one person, you may be right; for a large database with teams of developers writing code - I don't think so.
-- Posted via http://dbforums.comReceived on Tue Oct 21 2003 - 14:10:49 CEST