On 1/5/06, Cliff Wells <[EMAIL PROTECTED]> wrote: > As far as things like Basecamp go, at least part of the reason I'm not > using it myself is because of this attitude about data integrity. > Again, I think David is a brilliant guy, but that doesn't make up for > the years of domain-specific experience and wide user-base available to > the database developers. Any problem at the application layer (which is > where most problems seem to occur) can cause data integrity issues > unless the database itself is enforcing those rules. To be certain, I > can understand his reluctance to use stored procedures and would even > grant him that part of the argument. But foreign keys? Really. Those > belong in the database: they are *not* "business logic" nor are they as > easily (or efficiently, I might add) enforced from outside the database.
For the record, I'm a big fan of foreign key constraints, and I always use InnoDB tables when I use MySQL. Stored procedures is the place where I'm likely to draw the line (but i do know that there are places where even stored procedures make good sense). Kevin
