Re: What predicates the following relation represents
Date: Tue, 6 Apr 2004 13:40:46 +0100
"Paul" <paul_at_test.com> wrote in message
> --CELKO-- wrote:
> > If what we are calling "sales" in this example ought to be
> > "batch_size", then I have it. And my key would be both columns, as
> > you said.
> yep that was what I was meaning.
> Also the predicate could have been: "packets of PART are available for
> sale in batches of size SOLD". It's kind of pointless discussing whether
> relations are "legal" without knowing the real-world interpretation of
> the underlying predicate.
> Here's another question:
> Suppose I have a relation containing the tuple ('nuts', 25).
> If I then do an INSERT of the tuple ('nuts', 25) in SQL I get an key
> violation error (assuming the primary key is defined). In a truly
> relational DBMS, should it silently accept this, but just do nothing?
In a truly relational database, INSERT is a derived concept. Specifically it is a shorthand for an assignment. Whether or not you include a check for 'key violation' in that shorthand is of little import IMO.
Business Intelligence, IBM Global Services Received on Tue Apr 06 2004 - 14:40:46 CEST