Re: too much OOP ?

On Dec 28 2007, 12:20 pm, "Dmitry A. Kazakov" <mail...@dmitry-
kazakov.de> wrote:
On Fri, 28 Dec 2007 09:26:27 -0500, Daniel T. wrote:
Matthew Shelton <crash...@xxxxxxxxx> wrote:

I'm building a java/JSP webapp. So I have everything designed
pretty well, expecting usual code/test iterations.

I'm just wondering if OOP is a bit overkill for a database app.
I continue to end up with a utility class with a bunch of
static methods, no matter how I try to analyze it. as
everything is done one record at a time (inserts, searches,
updates.) so I don't really have a need for multiple instances
of a class. It seems pretty procedural, by nature.

Unlike the last responder, I have to say that it may very well be
the case that OO isn't appropriate for your application.

I don't think it is true, or better to say, it is true only because
these systems are designed at an extremely low abstraction level.
When the OP talks about "update query" it is an indicator of.
Another is "database application." Not uncommon, but it is actually
same as to talk about a "CPU application" and then to conclude that
there isn't much OO around "MOV" instructions. True, so what?
Should it be this way?

I hate to sound like I agree with topmind, and I have to admit that I
know almost nothing of the domain, but it seems to me that SQL is
pretty high level language in its own right.

.

Loading