On Fri, 25 Mar 2005, Kenneth Koenraadt wrote:
> On Thu, 24 Mar 2005 22:46:49 GMT, HansF <News.Hans_at_telus.net> wrote:
> You have an application. A minor correction must be made. It is now
> easier to implement a trigger instead of changing the code. So you do.
>
> Next time you need corrections, another trigger is implemented. And so
> you continue n times.
>
> You now have 2 tracks to housekeep: The original application code AND
> the triggers. One is flow-based, and one is event-based (the
> triggers). And those 2 tracks have to be coordinated. This will get
> more and more tedious over time, as the application logic changes over
> time, mostly in a more complicated direction.
>
> Result : More errors, more difficult and expensive application
> development. Which gets worse and worse over time. In that sense you
> have reduced scalability regarding your application's ability to
> implement changes over time.
I've heard this argument quite a few times, and it always came from
application developers that didn't understand database coding.
--
Galen deForest Boyer
Received on Fri Mar 25 2005 - 23:26:05 CST
