Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> comp.databases.theory -> Re: Generalised approach to storing address details

Re: Generalised approach to storing address details

From: Neo <neo55592_at_hotmail.com>
Date: 9 Dec 2006 09:46:46 -0800
Message-ID: <1165686405.928834.115510@l12g2000cwl.googlegroups.com>


> ... it has been established that [EAV] breaks the Information Principle.

>From prior posts, the definition of the Information Principle seems to
be: The entire information content of a relational database is represented in one and only one way: namely, as attribute values within tuples within relations.

This seems to imply that not matter how information is organized within a relational db, it is still represented as attribute values within tuples within relations. The Information Principle does not seem to say in any way that the way information is structured breaks that principle. In deed, even using EAV, the information content of that relational database is still represented in one and only one way: namely, as attribute values within tuples within relations.

Could you re-establish why EAV breaks the Information Principle? Better yet, could you show a simple EAV example that breaks the principle. Best yet, could you show any relational database that breaks the principle! Received on Sat Dec 09 2006 - 11:46:46 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US