Re: Clean Object Class Design -- What is it?

"Mikito Harakiri" <nospam_at_newsranger.com> wrote ...
> I see that in my organization:-( Most of the developers see relational
 database
> as some king of physical storage. They write multiple APIs to access the
 data
> (sometimes not only for modification, but for reading the data as well!).
 Some
> other groups write APIs upon those APIs and naively think that they raize
 the
> application abstraction level!

It goes without saying, of course, that if your developers are going to rewrite code several times to access data from the database, then you need data integrity checks in the database itself, to prevent some really nasty stuff from happening. The question is, if the data is globally accessible via a given API from a central location, through an OOP-style remote call interface, then why is this a bad thing?

> Where formerly I was able to quickly figure out
> the functionality from data model, I'm now forced to debug their spagetti
 code
> in order to understand how their dumb API works.

Is your criticism of the technique, then, that you think an object oriented programming API is harder to understand and use than a relational database? I'd think quite the opposite, to object oriented programmers. Or is your criticism that you don't like your developers, which no one can do anything about? I've met several relational database people that I don't like, too.

Chris Smith Received on Sun Jul 22 2001 - 01:33:54 CEST