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: TRM - Morbidity has set in, or not?

Re: TRM - Morbidity has set in, or not?

From: Marshall <marshall.spight_at_gmail.com>
Date: 19 May 2006 10:35:56 -0700
Message-ID: <1148060156.558158.142020@j73g2000cwa.googlegroups.com>


Bob Badour wrote:

>

> You will often hear people speak of "impedance mismatch". Many people
> think the way to address that problem is to lower the data language to
> the level of existing programming languages.

This is one of the biggest annoyances in my professional life.

Example:

me: ... and we can get rid of this attribute, because we already   have uniqueness from these attributes over here. them: oh, but our framework requires an integer primary key.

Or whatever. "Our framework requires" some crap. Well, your framework sucks then. Why don't you ditch it and write some good code instead?

Or they've layered the dbms under so much crap until it's like a babe in a burqa, and they can't even tell any more when they call this method or that method that it's doing network access, so they write code like

fetch list of primary keys
for each key {
  fetch that row
  update one attribute
}

... and end up doing 10,000 jdbc calls when they could have done it in one.

Not that I am bitter.

Marshall Received on Fri May 19 2006 - 12:35:56 CDT

Original text of this message

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