Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> comp.databases.theory -> Re: The wisdom of the object mentors (Was: Searching OO Associations with RDBMS Persistence Models)

Re: The wisdom of the object mentors (Was: Searching OO Associations with RDBMS Persistence Models)

From: David Cressey <dcressey_at_verizon.net>
Date: Thu, 01 Jun 2006 18:35:58 GMT
Message-ID: <isGfg.259$Jm5.166@trndny08>

"Tony Andrews" <andrewst_at_onetel.com> wrote in message news:1149163087.832586.36310_at_u72g2000cwu.googlegroups.com...
> frebe73_at_gmail.com wrote:

> One could argue that to the UI programmer, the database is a "bit
> bucket" (very ugly term) of which he/she needs to know little.
> However, the UI is probably only 10-20% of the code, with 80-90% being
> the database application code - and to write this well you need to know
> your DBMS.

The problem with the above is this:

The UI programmer thinks he/she is on the outside of a capsule that he/she is really on the inside of.

The problem with the concept of encapsulation is that outside and inside are not symmetric, but there is no objective method of determining which is which.

>
> This is a lot different from RCM's stance (as I understand it), which
> is that even the developer writing the database code - the "guts" of
> the data processing - shouldn't need to know anything about the DBMS.
> I don't agree with this.
>

The DBMS has "public parts", which an app programmer should know, and "private parts' which an app programmer, in general, has no need to know, and may have a need not to know. Received on Thu Jun 01 2006 - 13:35:58 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US