-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/09/07 10:50, Erik Jones wrote: > > On Apr 9, 2007, at 9:46 AM, Vivek Khera wrote: [snip] >> One thing that was really counter-intuitive to me from a guy who runs >> really large databases, was to get rid of some of the FK's and manage >> them in the application layer. This one scares me since I've had my >> behind saved at least a couple of times by having the extra layer in >> the DB to protect me... the data integrity would be managed by some >> external program that sweeps the DB every so often and purges out data >> that should no longer be there (ie stuff that would have been CASCADE >> DELETEd). > > This is often debated and it does seem strange to here that stance from > a dba. It's normally the application developers who want to do that. It depends on how efficient your engine and site are at deleting cascades. If it causes an unacceptable amount of extra locking in a multi-user situation, away goes the FK and in comes the off-hour sweeper. - -- Ron Johnson, Jr. Jefferson LA USA Give a man a fish, and he eats for a day. Hit him with a fish, and he goes away for good! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGH41yS9HxQb37XmcRArGnAJ4n12NxeKleCf7n1OFUtOQYnJy1wQCg6OVz fMjwTsezDnukoV8yyXTouJw= =XgVW -----END PGP SIGNATURE-----
