Re: Navigation vs Relational operators
From: Tony <andrewst_at_onetel.net.uk>
Date: 17 May 2004 08:45:52 -0700
Message-ID: <c0e3f26e.0405170745.7f1c44b4_at_posting.google.com>
Date: 17 May 2004 08:45:52 -0700
Message-ID: <c0e3f26e.0405170745.7f1c44b4_at_posting.google.com>
"x" <x-false_at_yahoo.com> wrote in message news:<40a884b6_at_post.usenet.com>...
> Well, we don't need to tell the driver how to drive.
> But we may need to tell him (some of) the route ...
Not necessarily. London taxi drivers, for example, are expected to know their way around London. If you got into a taxi at Trafalgar Square and said "take me to Heathrow Airport", you would *not* expect the driver to ask you for directions! Think of the database as the taxi driver's "patch" and the DBMS as the taxi driver; SQL is the instruction you give the taxi driver. There is no need to specify navigation details, because the driver (DBMS) knows his "patch" (the database) well. Received on Mon May 17 2004 - 17:45:52 CEST