Re: foundations of relational theory?

"Patrick Payne" <patrickpayne_at_yahoo.com> wrote in message news:b6da8ff0.0311051706.3e048add_at_posting.google.com...
> Instead we develop business modules that the user
> calls.

By this you mean an ad-hoc api for updating the db, right?

> This model has the advantages of Forced Data Integrity,

What does that mean? That data access is mediated through procedurally written code? As I've argued before, this is distinctly worse than declarative integrity constraints.

> the end user does not have to know our data model.

But they do have to learn your API, right? How is that any better?

> Essentially it creates
> customized mini-sql engines for our data objects.

Except it's never fully general. You have to manually create each kind of insert, update, delete, and query. You have to consider ahead of time what kinds of bulk operations you're going to support. For each and every operation, you have to manually write procedural code to enable it. Any ones that you don't think of ahead of time, the application can't do. Whereas if you exposed SQL, you'd have full generality no matter what, at no effort.

I don't see any advantages; in fact, it seems a lot worse.

Marshall Received on Thu Nov 06 2003 - 06:22:18 CET