Re: Very simple question to relational theorists.
Date: Sat, 18 Aug 2012 00:29:29 -0700 (PDT)
Message-ID: <505b88d0-cb66-4df8-bbf4-9fa83eeb348e_at_googlegroups.com>
On Friday, August 17, 2012 4:14:04 PM UTC-7, Evgeniy Grigoriev wrote:
> 1) About this thread. Here I just want to show that I can use such complex names to name relational attributes.
Understand.
> 3) About predicates and what I must associate with relation. Relational data model is abstract mathematics. Relation is a formal and meaningless data structure. If a data structure is equal to formal definition of a relation (I prefer to use the one given in "The Theory Of Relational Database" by David Maier) it is a relation. Relation doesn't have to tell something to DBA about the world to be relation. It's not only my viewpoint (http://www.dbdebunk.blogspot.com/2012/07/meaning-and-database-management.html#more)
I repeat, just using relations is **not** being relational.
The Maier book begins with "Each row in the table summarizes some object or relationship in the real world." At the dbdebunk link Hugh writes "The meaning of relation SP as understood by the user is: Supplier S# supplies part P# in a quantity of QTY". A formal system does not know meanings, but it produces meanings given other meanings. Codd's relation operators are designed specifically so that if the value of a relation is the set of all tuples that make its predicate true then a query result is the set of tuples that make its predicate true. That query meaning is in terms of the meanings of relations and meanings of the relation operators.
I'll look.
> By the way, from my viewpoint the relation
> (1+2) 'DOC(ID, .No, .Lines.Item , .Items,Qty)
> is full of sence.
Yes, I expect that it is. And I expect that its meaning is in terms of the meaning of DOC.lines and the other dotless-attribute DOC and whatever special operator you are offering that produced it from them.
philip Received on Sat Aug 18 2012 - 09:29:29 CEST