Re: Storing derived and derivable data

From: Jan Hidders <hidders_at_gmail.com>
Date: 30 Apr 2006 07:04:27 -0700
Message-ID: <1146405867.756355.5100_at_j33g2000cwa.googlegroups.com>

dawn wrote:
> Is there database theory that includes identification of
>
> 1. the fact that values for an attribute either were or could have been
> derived?
> 2. how values for an attribute were derived?
> 3. how values for an attribute could have been derived?

That is usuallly taken care of by specifying the database constraints that define the relationships between the derived column and the other data, and then marking it as either derived or not.

This is rather trivial. So I'm wondering if I understood your question correctly.

Jan Hidders

Received on Sun Apr 30 2006 - 16:04:27 CEST

This message: [ Message body ]
Next message: Jan Hidders: "Re: Functional dependency is multivalued dependency"
Previous message: Jan Hidders: "Re: Lucid statement of the MV vs RM position?"
In reply to: dawn: "Storing derived and derivable data"
Next in thread: Jan Hidders: "Re: Functional dependency is multivalued dependency"

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]

Original text of this message