Re: Navigation question
Date: Sun, 18 Feb 2007 13:44:52 GMT
Message-ID: <oLYBh.902$aM.507_at_trndny03>
> All this talk of "nodes", and "then", and "going to" and so on -
> that's not what's happening. There is no "moving finger" that you
> guide through the database from table A to table B. You are issuing
> multiple independent queries with (hopefully) increasingly defined
> parameters. There is no connection between them, other than some
> shared parameters. Even in an SQL DBMS, you *cannot* "navigate" around
> tables.
It is possible to write Oracle applications that proceed in precisely this fashion. I have seen them. They are lousy. They deliver bad performance. They are hard to learn. They are difficult to modify.
In general, they fail to deliver the "bang for the buck" that proponents
claim for the relational model.
They combine all the inflexibility and opaqueness that traditional graph
based DBMS applications suffered from with the performance cost of using
indexes instead of pointers embedded in records.
Anybody who goes about things this way will, unless she sees and understands a well built Oracle application, conclude that the relational model was one big mistake. I'm using Oracle just for the sake of example. You can substitute any of a dozen other products, and my comments still aply.
The fact that thousands of other poorly built applications were built in the same time frame doesn't detract from the possibility of doing things right, even though the soi disant "relational DBMSes" have flaws, even major flaws, that c.d.t. discusses regularly. Received on Sun Feb 18 2007 - 14:44:52 CET