Re: Codd's Information Principle
- From: Bob Badour <bbadour@xxxxxxxxxxxxxxxx>
- Date: Sun, 01 Nov 2009 18:26:15 -0400
paul c wrote:
Bob Badour wrote:
paul c wrote:
...
Didn't mean to suggest otherwise. Sometimes the immediate expert objection to the 'primrose path' turns out to be an advantage if the idea is allowed to breath.
But one point seems very immediate to me - for any given relational expression, there is only one equivalent extension.
I don't follow that at all.
If you mean the last sentence, I could expand it by saying that for any given purpose, in other words any given application, I think that single extension must have one interpretation. Since the expression might not involve any algebraic operations, I think it is best to discard those in the interpretation, no matter how the extension was formed. I say 'best' because that seems sufficient to me and I don't see how including those ops is necessary. I would like to know what problems this causes, eg., I don't see that inconsistences/contradictions or loss of utility or inability to optimize result from it.
I cannot make sense of what you wrote.
.
- Follow-Ups:
- Re: Codd's Information Principle
- From: paul c
- Re: Codd's Information Principle
- References:
- Re: Codd's Information Principle
- From: compdb
- Re: Codd's Information Principle
- From: paul c
- Re: Codd's Information Principle
- From: Bob Badour
- Re: Codd's Information Principle
- From: paul c
- Re: Codd's Information Principle
- From: Bob Badour
- Re: Codd's Information Principle
- From: paul c
- Re: Codd's Information Principle
- Prev by Date: Re: Codd's Information Principle
- Next by Date: Re: foreign key constraint versus referential integrity constraint
- Previous by thread: Re: Codd's Information Principle
- Next by thread: Re: Codd's Information Principle
- Index(es):
Relevant Pages
|