508 Definitions
These are in no particular order - just as I think of them.
- Assuming that all queries specify one field, and that pi is the probability that fi is the field specified, and that we have 2B buckets and k fields, the number of bits of the address to assign to each field in order to minimize the average search time is given by
bi = (B - sum over j of lg pj) / k + lg pi
- Assuming that queries specify one or more fields, and that pi is the probability that the value of that field is known, and that we have 2B buckets and k fields, the number of bits of the address to assign to each field in order to minimize the average search time is given by
bi = (B - sum over j of lg (pj / (1-pj)) / k + lg (pi / (1-pi) )
- Physical data independence refers to when changes in the physical
level organization of a database do not affect the logical level.
- Logical data independence refers to when modifications to the logical
level structure do not affect existing view structures.
- Given a collection of sets D1, D2, ..., Dn
(not necessarily distinct), R is a relation on those sets if it is a set
of ordered n-tuples <d1, d2, ..., dn>
such that di is an element of Di, 1<=i<= n.
- A record is composed of fields. The manner in which the fields are organized within the record is called the record structure.
- A file is composed of records. The manner in which the records are organized within the file is called the file structure.
- An ISAM file has three parts: the main file, the index file and the overflow file.
- An attribute value is atomic if it is non-decomposable.
- A relation is normalized or in first
normal form is every attribute value in each tuple is atomic. A relvar is in first normal form if any reasonable relation created with that relvar would be normalized.
- A key or candidate key is a
non-redundant set of attributes that have unique values in each tuple of the
relation. One candidate key is chosen to be the primary key. The other
keys are referred to as alternate keys.
- Integrity refers to the fact that the data is correct. There are many ways to enforce integrity including (but not limited to) entity integrity, functional dependecies, referential integrity and domains.
- Entity Integrity: no component of a primary key value may be null.
- Referential Integrity: if an attribute, which is a primary key in one
relation, occurs in a second relation, then the values of that attribute in the
second relation must occur in the first relation.
- A given domain may optionally be designated
as primary iff there exists some single-attribute primary key defined on
that domain.
- A given attribute is prime if it is part of a key.
- If r(A1...An) is a
relation and Di = dom(Ai) 1 <= i <= n, then the active domain of Ai relative to r is the
set
- Let adom(R,r) be the set of all tuples over
the attributes of R and their active domains relative to r. The active
complement of r is
- The notation r(R) means that r is a relation with relvar R.
- Let r(R) be a relation, A is an element of R,
a is an element of dom(A). Then restrict(select) A equal to a on r, written
, is defined as
- Let r(R) be a relation, X is a subset of R. The projection of r onto X, written ΠX(r), is
the relation
- Given r(R) and s(S) are relations and T=R ∪ S, the join of r and s, r><s, is the
relation
- Let q(RS) be a relation, with r= ΠR(q)
and s= ΠS(q). Let
q'= r><
s. If q=q', then q decomposes losslessly onto R
and S.
- The project-join procedure is idempotent
(the result of applying it n times is the same as the result of applying it
once.)
- A constant relation is one where the tuple values are fixed.
- Let r(R) be a relation, A ∈ R, and B ∉ R-A and dom(A)=dom(B). Let R'=(R-A)B.
Then r with A renamed to B, denoted δA<-B
(r) is the relation
- Let r(R) and s(S) be relations, with S⊂ R. Let R'=R-S. Then r divided by s,
is the relation
- Let r(R) and s(S) be relations, R ∩ S = ∅, with Ai∈
R, Bi∈S and
dom(Ai)=dom(Bi), 1<= i <=m. The Ai's
need not be distinct, nor need the Bi's. The equijoin of r and s
on A1...Am and B1...Bm written r[A1=B1,...,Am=Bm]s
is the relation
- Let r(R) and s(S) be relations, R∩
S = ∅. Let A∈ R and B∈ S be ρ-comparable for ρ∈
Θ. Then the theta-join
of r and s on A and B, written r[AρB]s, is the relation
- Let r(R) be a relation with X∈
R and Y∈ R. Relation r satisfies the functional dependency
X->Y if for every x∈X, has at most one tuple.
- We have a functional dependency of Y
on X if any relation r (which is meaningful) on R will satisfy X->Y.
- Given a set of functional dependencies F, and
X->Y ∈
F+, Y is partially dependent upon X
under F if X->Y is not left reduced. If X->Y is left reduced, then Y is fully
dependent on X.
- X->Y is left reduced if there does
not exist any X'∈
X such that X'->Y.
- Given a relvar R, A ∈
R, and a set F of functional dependencies over R, A is prime in
R with respect to F is A is contained in some key of R. Otherwise A is nonprime in R.
- A relation scheme R is in second normal
form with respect to a set of functional dependencies F if it is in first
normal form and every nonprime attribute is fully dependent on every key of R.
- Given a relation scheme R, X∈R
, A∈R
, and a set of functional dependencies F, A is transitively
dependent on X in R if there is a subset Y of R such that,
X->Y, Y !-> X, and Y->A under F and A ∉ XY
- A relation scheme R is in 3NF with
respect to a set of functional dependencies F if it is in 1NF and no nonprime
attribute in R is transitively dependent upon a key of R.
- A relation scheme R is in Boyce Codd
Normal Form if whenever Y->A holds, A ∉ Y, then Y is or
contains a key of R.
- Let r(R) be a relation, A⊂R
, B⊂R,
C=R-AB. The multi-valued dependency,
A->>B holds iff for every t1,t2∈
r, with
t1(A)=t2(A) then ∃
t3,t4∈r
such that t1(A)=t3(A)= t4(A) and t1(B)=t3(B)
and t2(C)=t3(C) and t2(B)=t4(B) and
t1(C)=t4(C).
- X->>Y is trivial if for any
R with XY∈
R, any r(R) satisfies X->>Y.
- A relvar is in 4NF with
respect to a given set of functional dependencies and multivalued dependencies
iff it is in 3NF and for every MVD X->>Y, either the MVD is trivial or X
is or contains a key of R.
- Let {R1,R2,...,Rp} be a set of
relvars over U. A relation r(U) satisfies the join dependency,
*[R1,R2,...,Rp] if r decomposes losslessly onto R1,R2,...,Rp.
- A join dependency is trivial if R=Ri for some 1≤i≤p or if every Ri contains a key of U.
- Let R be a relvar and let F be a set
of fd's and jd's over R. R is in 5NF with respect to F if for every JD
implied by F that applies to R, the JD is trivial.
The End - I ain't goin' to do no mor'!