Re: Relation Schemata vs. Relation Variables
- From: Bob Badour <bbadour@xxxxxxxxxxxxxxxx>
- Date: Thu, 24 Aug 2006 23:23:01 GMT
paul c wrote:
paul c wrote:
...
PMFJI, I would say that the VALUE of a candidate key identifies one and only one tuple FOREVER!
Stupid me, I have to take part of that back - the value of a candidate key obviously could identify several tuples but I still think that would hold forever. Might have been better to say the value of a candidate key identifies a tuple regardless of time.
A candidate key does not identify a tuple. A candidate key is a constraint on a relvar and not on a tuple.
.
- Follow-Ups:
- Re: Relation Schemata vs. Relation Variables
- From: paul c
- Re: Relation Schemata vs. Relation Variables
- References:
- Relation Schemata vs. Relation Variables
- From: Brian Selzer
- Re: Relation Schemata vs. Relation Variables
- From: JOG
- Re: Relation Schemata vs. Relation Variables
- From: Brian Selzer
- Re: Relation Schemata vs. Relation Variables
- From: JOG
- Re: Relation Schemata vs. Relation Variables
- From: JOG
- Re: Relation Schemata vs. Relation Variables
- From: brian
- Re: Relation Schemata vs. Relation Variables
- From: David Cressey
- Re: Relation Schemata vs. Relation Variables
- From: brian
- Re: Relation Schemata vs. Relation Variables
- From: paul c
- Re: Relation Schemata vs. Relation Variables
- From: paul c
- Relation Schemata vs. Relation Variables
- Prev by Date: Re: Relation Schemata vs. Relation Variables
- Next by Date: Re: Relation Schemata vs. Relation Variables
- Previous by thread: Re: Relation Schemata vs. Relation Variables
- Next by thread: Re: Relation Schemata vs. Relation Variables
- Index(es):
Relevant Pages
|