Re: Use of the term "hierarchy"
- From: "Marshall Spight" <marshall.spight@xxxxxxxxx>
- Date: 28 Aug 2005 17:50:51 -0700
Kenneth Downs wrote:
>
> SELECT *.employee
> WHERE project_start < '2005-11-15'
>
> the the table-column-oriented system infers that you mean to pull and UNION
> the results from all tables having columns employee code and project_start?
The concern I have with this idea is that is has so much
in the way of non-local effects. One is pulling in data
from essentially the entire namespace. It's not clear to
me that one wants to have the requirement that the
namespace be fully unified; that every "employee" attribute
has to mean the same thing. Scope is a good thing.
Also a non-local effect: the creation of a new table with
the appropriately-named attributes changes the meaning
of this query. It's essentially implicitly dependent on the
entire schema. That's hard to control.
Marshall
.
- Follow-Ups:
- Re: Use of the term "hierarchy"
- From: Kenneth Downs
- Re: Use of the term "hierarchy"
- References:
- Use of the term "hierarchy"
- From: Kenneth Downs
- Re: Use of the term "hierarchy"
- From: Marshall Spight
- Re: Use of the term "hierarchy"
- From: Alexandr Savinov
- Re: Use of the term "hierarchy"
- From: Kenneth Downs
- Use of the term "hierarchy"
- Prev by Date: Re: Modeling Address using Relational Theory
- Next by Date: Re: Modeling Address using Relational Theory
- Previous by thread: Re: Use of the term "hierarchy"
- Next by thread: Re: Use of the term "hierarchy"
- Index(es):
Relevant Pages
|