Terminology Question: Intention and Extension
From: Rob <rmpsfdbs_at_gmail.com>
Date: Sat, 5 Apr 2008 10:05:42 -0700 (PDT)
Message-ID: <31c927f4-e69d-4b33-9cbc-7f3fb082c0ea_at_e10g2000prf.googlegroups.com>
In the early days of the relational model, the words *intention* and "extension* were used respectively to mean *query* and *response*. That is, an SQL (or other database language) query represented your *intention*, that which defined what you wanted to retrieve. What the RDBMS delivered to you was the corresponding *extension*. (Kind of like the definition of something and the thing itself.)
Date: Sat, 5 Apr 2008 10:05:42 -0700 (PDT)
Message-ID: <31c927f4-e69d-4b33-9cbc-7f3fb082c0ea_at_e10g2000prf.googlegroups.com>
In the early days of the relational model, the words *intention* and "extension* were used respectively to mean *query* and *response*. That is, an SQL (or other database language) query represented your *intention*, that which defined what you wanted to retrieve. What the RDBMS delivered to you was the corresponding *extension*. (Kind of like the definition of something and the thing itself.)
Is this usage (query = intention, response = extension) used today? If not, what are the common terms used for query and response, and how are the terms *intention* and *extension* used now? Received on Sat Apr 05 2008 - 19:05:42 CEST