Re: Object-relational impedence

On Mar 3, 3:11 pm, Robert Martin <uncle..._at_objectmentor.com> wrote:
> On 2008-03-03 12:29:02 -0600, TroyK <cs_tr..._at_juno.com> said:
>
> > My experience is somewhere between 2 and 3 orders of magnitude
> > difference between implementing a business rules change in the db vs.
> > the programming team doing it in OO code.
>
> Then you should be able to fly rings around the programmers and get
> them all fired.  Why haven't you?

If by "fly rings around the programmers" you mean having a fully functioning reference implementation up and running in SQL within 2 weeks that ends up taking a team of 3 programmers over 3 months to implement in code, then, yeah, I guess I do. But the architecture called for the programming to be done in a business layer implemented in C# -- we expected and planned for that, so, happily, no one gets fired.

> Ladies and gentlemen, there are certainly tasks that are better suited
> to SQL and stored procedures.  There are other tasks that are better

Who said anything about stored procedures? I'm talking about implementing the business rules via constraint declaration in the database, and deriving new values throught the application of SQL queries.

> suited to general purpose languages.  True wisdom comes from knowing
> the strengths and weaknesses of both.  Good architects build systems
> that combine the tools synergistically.

And good agile programmers know to use a high-level language in order to enable iterating over design at a rapid pace.

TroyK Received on Wed Mar 05 2008 - 00:29:01 CET