Re: Navigation vs Relational operators

• Post for FREE via your newsreader at post.usenet.com ****

"Mike Nicewarner" <psyclo_at_nospam_datamodel.org> wrote in message news:c8acu6$9ft$1_at_news.netins.net...
> Interesting discussion.
> The idea of suggesting a route to the taxi driver is like suggesting index
> usage to some DBMS. Sometimes we force a specific order of operation by
> placement of subqueries. In any event, the DBMS/taxi driver makes the
final
> decision about how to get the data.
> And remember that in many situations, the data is no where near where you
> think it is. Think "bufferpools" or other caching ideas. In other words,
> "LAX" isn't always at the same location, so for you to force the taxi
driver
> to take a specific route might be the worst idea possible.

Well, the taxi driver know the names of the places and streets (our own names, not city hall names).
When we tell him the "route", we use these names. What I have in mind , it is more like specifying attributes and join conditions.

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

• Usenet.com - The #1 Usenet Newsgroup Service on The Planet! *** http://www.usenet.com Unlimited Download - 19 Seperate Servers - 90,000 groups - Uncensored -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=