Re: Databases as objects

From: Bob Badour <bbadour_at_pei.sympatico.ca>
Date: Fri, 22 Dec 2006 18:43:58 GMT
Message-ID: <OHVih.36300$cz.535302@ursa-nb00s0.nbnet.nb.ca>

Gene Wirchenko wrote:

> Thomas Gagne <tgagne_at_wide-open-west.com> wrote:
>
> [snip]
>

>>At some point, all that expression and composition has an ingress and 
>>egress, and what lies between them is a reusable, repeatable code.  No 
>>one really wants to write all that SQL by hand every time so it's put 
>>inside a macro.  To increase the macro's value parameters are applied to 
>>make it a function.  Now we're cooking with fire.


> 

>      I think you  are going in the wrong direction.

> 

>      All what SQL?  The SQL in my app is a very small part of it.  The

> presentation code is much, much bigger. It is the presentation code
> that I would like to cut down.
>
> [snip]

UI code and exception-handling code account for the bulk of most applications (and a disproportionate amount of bugs.) Received on Fri Dec 22 2006 - 12:43:58 CST