Re: Databases as objects

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

>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.
>>
>In my commercial finance system, 37% of the source code is SQL. 43% is
>presentation (PHP). When you say your SQL is a small amount, what does
>that mean? Are able to count it?

     That it is a very small percentage. Certainly under 10%.

Sincerely,

Gene Wirchenko

Computerese Irregular Verb Conjugation:

     I have preferences.
     You have biases.
     He/She has prejudices.