Re: Navigation question
Date: Sat, 03 Mar 2007 00:45:32 GMT
Message-ID: <My3Gh.55$ig.31_at_trndny01>
> Actually, I would say that Tony D gave the definitive answer on February
> 16 at 1:52pm.
In Google groups, I found an answer from Tony D at 12:52 PM. I assume
that's the one.
Here's an excerpt:
<quote>
Dawn, this probably is the definitive answer. You need to understand this
Probably because you *can't* "navigate" around an SQL database in the
way you would navigate in a car. There are no predetermined routes
that you must follow; you can join tables using whichever columns you
like, and leave the DBMS to worry about how it will be done. If you
really must persist with a car driving metaphor, consider the DBMS as
your taxi driver and the query optimizer his GPS. You ask him to take
you to the store, but you don't sit behind him telling him when to
take a left.
<end quote>
and demonstrate an understanding, before I'm going to invest any more time
in trying to discuss this with you.
>
>
> >>(that is, I don't care if it sequentially reads
> >>the entire medium multiple times at the physical layer, but to the
> >>developer the database is navigated). If no one can give an example
> >>of bad navigation (at the logical level), then could someone at least
> >>tell if either or both of the examples I have provided for navigation
> >>are bad and, if so, why.
> >
> > If there is no navigation at the logical level, then there is no bad
> > navigation at the logical level.
> >
> >
> >>I very much appreciate any effort given to try to help me understand
> >>more precisely what database navigation is considered bad and why.
>
> What a lying sack of shit. Anyone with half a brain can see she has no
> fucking intention of every understanding a goddam thing and she never had.
>
>
> > Address based access.
>
> Why, oh why, must you feed the troll? Do you do it to annoy everyone else?
Received on Sat Mar 03 2007 - 01:45:32 CET