Re: S.O.D.A. database Query API - call for comments
Date: Sat, 21 Jul 2001 18:01:50 GMT
Message-ID: <9cuuue$ks4$1_at_geraldo.cc.utexas.edu>
In comp.databases Tobias Brox <tobiasb_at_suptra.org> wrote:
: Certainly table rows contain relations that should tell something about
: the real world. And certainly it's possible to store objects as one or
: more table rows.
: Anyway, I think that a table row is close to worthless if you
: encapsulate it into an object in the database. I see no need to do
: that. Beeing able to join tables and do small selections is the major
: power with the relational model.
: Said another way; the resulting rows from a query is usually very
: interessting, but often the "raw" rows of a base table doesn't belong
: anywhere else than in the database, ready to be used by queries.
This is quite insightful. I wish I could have read this first, and saved us all some typing.
:> We like to call that a function, or a stored procedure according to your :> flavor.
: Function, procedure, stored procedure, method ... what to call it only
: depends on the paradigm. For SQL and DBMS'es, I'd call it "stored
: procedures", when beeing object oriented, it's "methods".
Yes, the point being, why so much carping in the OODBMS camp about methods, when other DBMS types have the same functionality?
:> Your co-workers were fools. I do not say this to insult, only to be :> honest. I have run into this myth several times in my career, and it is :> always hard to convince beginning programmers otherwise.
: He was certainly very stubborn, and I was very amuzed both at this point
: of view and many other viewpoints of him.
I'm developing a mental picture...
: I don't think he was right in the case where two tables should be
: joined, but he certainly was right when subqueries were involved. The
: DBMS stalled completely. It went pretty fast through perl, as long as
: the subquery didn't have a too big return-set.
*boggle*
: Besides, that rotten DBMS we used probably hasn't existed for 20 years
: :-)
Hot damn!
: God knows why we used it. When I asked the abovementionated collegue
: about his plans for changing it out, he said he was already working with
: it - changing it out to flat files, not to another DBMS.
Double hot damn!
I feel your pain.
Have you tried any more modern RDBMSes?
Received on Sat Jul 21 2001 - 20:01:50 CEST