Re: You have my sympathies

nsouto_at_nsw.bigpond.net.au.nospam (Nuno Souto) writes:

> On Tue, 14 Mar 2000 16:06:15 GMT, "James Moore" <james_at_banshee.com>
> wrote:
>
> >To me, the use of triggers and stored procedures is something to be avoided,
> >not sought out. As much as possible should be done by the application. The
> >big downside of things like stored procedures and triggers is that they're
> >written in some non-standard extension to SQL. There's no standard way to
> >write database code inside databases; Oracle, Sybase, Microsoft and the
> >others all have their own way of doing things. Instead of using these, do
> >the work in your application instead.
>
> For a variety of reasons that take too long to explain, that is the
> completely wrong attitude to writing portable code, and one of the
> reasons for the code bloat that is seen nowadays in so many
> third-party applications. And the buggy code too.

While a long dissertation on the pitfalls to be avoided and the benefits to be achieved by writing database-side procedures and triggers may be uncalled for, I'd love to see some people put forth at least a list of such justifications. I think it would be and excellent subject of converstation. It would also help a lot of people (myself included) sell The Powers That Be, on what many of us consider a sensible approach to database development.

-Andy U Received on Wed Mar 15 2000 - 10:45:59 CST