Arthur Fuller
fuller.artful at gmail.com
Mon Jul 27 13:11:39 CDT 2009
I waited for the second coming of several women in my life, but I digress. This whole line of argument is IMO dangerous, treacherous, distributive of the responsibilty and location of the code, and perhaps a few other adjectives. I know that lots of you don't agree with me, but I will cite this whole thread as evidence in favor of my stance on this. Database code should reside in exactly one place -- the database. Stored procedures, triggers, event schedules, views, roles, security and so on should exist only in the database. Dynamically constructed SQL statements should be cause for the death penalty unless their coders can prove there is no other way to achieve the desired result. Ok. I'm all tuckered out. Just let me recap in one sentence: Everything the database *can* do, the database *should* do. Arthur