CSE 414 Section 6
BCNF & Transactions
11/3/22
Announcements
Brief Recap
Functional Dependencies
A functional dependency (FD) for relation R is a formula of the form A → B
where A and B are sets or individual attributes of R.
We say the FD holds for R if, for any instance of R, whenever two tuples agree in value for all attributes of A, they also agree in value for all attributes of B.
DEPENDENCY != CAUSATION
*in other words: A determines B, or A is kinda sorta a key for B
Closures
Goal:
Observation:
Keys
We call an attribute (or a set of attributes) that determines all other attributes in a schema to be a superkey.
If it is the smallest set of attributes (in terms of cardinality) that does this we call that set a minimal key or just key
By definition, all minimal keys are superkeys, but a superkey is not necessarily a minimal key.
Boyce-Codd Normal Form (BCNF)
A relation R is in BCNF if every set of attributes in R is either a superkey or its closure is the same set (trivial FD).
*that is, either {a}+ -> a OR {a}+ -> {all cols}, where a is any col in the table
Boyce-Codd Normal Form (BCNF)
Not BCNF! SSN is not a trivial FD or a superkey
BCNF Decomposition Algorithm
X +
BCNF Decomposition Algorithm
C = the set of all attributes in the relation R
Look for an attribute (or a set of attributes) that meets the following conditions (non-BCNF flag!):
If such attribute exists, it is a violation of the BCNF condition; decompose R:
Else, the table is in BCNF
Example
Relation: R (A, B, C, D, E)
FDs:
Goal: Decompose R into BCNF
Example
R (A, B, C, D, E)
R (A, E)
R (A, B, C, D)
R (B, C, A)
R (B, C, D)
A+ = {A, E}
BCNF compliant
BCNF compliant
BCNF compliant
{B, C}+ = {B, C, A}
Solution
Notice that {A}+ = {A,E}, which violates the BCNF condition
Notice there is no E in R2 so we don't need to consider FD DE → B
Motivation for Transactions
ACID
Atomic�Consistent�Isolated�Durable
Everything a concurrent database user wants…
How do ACID properties help us?
Atomicity
What? “Atom” - a transaction is indivisible; data operations inside the transaction work in an all or nothing fashion
How? Transaction commit and rollback
Example: Transfer of funds from one account to another involves an atomic transaction that includes operations of debit and credit
Consistency
What? Only data operations that comply with database validity constraints are allowed.
Once a transaction is completed, it must not leave the database incomplete or inconsistent.
How? Enforcement of consistency rules upon data entry/updation
Example: A database having both first and last name fields will not accept if you enter only one of those - must enter both for the transaction to be complete
Isolation
What? The appearance of a transaction happening by itself irrespective of what other transactions are happening concurrently
How? User views the database that was present right before the view request is made and any further transactions that are in process after it are ignored
Example: A teller looking up a balance must be isolated from a concurrent transaction involving a withdrawal from the same account
Durability
What? Once a transaction is complete the information as changed will survive failures of any kind
How? Creation of data “mirrors”
Example: Trying to make an update that leads to a system failure should not tamper with any of the previous data and transactions
Txn Perspective
A database is a collection of "elements" that can be written to or read from.
Operation - A read or write to an element (later: or an insert or delete)
Example: What operation does the following SQL query contain?�SELECT cases FROM Country WHERE cname = ‘France’;
Txn Perspective
A database is a collection of "elements" that can be written to or read from.
Operation - A read or write to an element (later: or an insert or delete)
Example: What operation does the following SQL query contain?�SELECT cases FROM Country WHERE cname = ‘France’;
Answer: R(Country) or R(France), depending on whether the "element" is a table or a row (assuming cname is a key). Let's go with the finer-grained element.
Practice - convert SQL to operations
Txn 1:
1a) x = SELECT cases FROM Country WHERE cname = ‘France’;
1b) x = x + 200;
1c) UPDATE Country SET cases = `x` WHERE cname = ‘France’;
Txn 2:
2a) y = SELECT cases FROM Country WHERE cname = ‘Spain’;
2b) y = y / 5;
2c) z = SELECT cases FROM Country WHERE cname = ‘France’;
2d) UPDATE Country SET cases = `y + z` WHERE cname = ‘France’;
Practice - convert SQL to operations
Txn 1:
1a) x = SELECT cases FROM Country WHERE cname = ‘France’;
1b) x = x + 200;
1c) UPDATE Country SET cases = `x` WHERE cname = ‘France’;
Txn 2:
2a) y = SELECT cases FROM Country WHERE cname = ‘Spain’;
2b) y = y / 5;
2c) z = SELECT cases FROM Country WHERE cname = ‘France’;
2d) UPDATE Country SET cases = `y + z` WHERE cname = ‘France’;
1a) R(France)
1b)
1c) W(France)
2a) R(Spain)
2b)
2c) R(France)
2d) W(France)
Definitions
Operation -
Transaction -
Schedule -
Serial schedule -�
Serializable schedule - �
Definitions
Operation - read or write of an element (later: insert or delete)
Transaction - series of operations meant to have the ACID guarantees
Schedule - ordering of the operations of some txns
Serial schedule - schedule where each txn is executed one after another.� No interleaving
Serializable schedule - a schedule that is behaviorally equivalent � to a serial schedule
Worksheet