Beginning SQL

Chapter 4
152
SELECT * FROM MemberDetails;
DROP TABLE MemberDetails;
CREATE TABLE MemberDetails
(
MemberId integer NOT NULL,
FirstName vargraphic(50) NOT NULL,
LastName vargraphic(50) NOT NULL,
DateOfBirth date,
Street varchar(100),
City varchar(75),
State varchar(75),
ZipCode varchar(12),
Email varchar(200),
DateOfJoining date
);
INSERT INTO MemberDetails
SELECT * FROM TempMemberDetails;
DROP TABLE TempMemberDetails;
Once the NOT NULL constraints are in place, you can add the index again:
CREATE UNIQUE INDEX member_name_indx
ON MemberDetails (LastName DESC, FirstName);
Finally, define the relationships between tables by adding FOREIGN KEY constraints. Figure 4-1 shows
the foreign key links, and the following list reiterates them.
❑ The CategoryId column in the Films table is a foreign key linking to the CategoryId column in
the Category table.
❑ The CategoryId column in the FavCategory table is a foreign key linking to the CategoryId column
in the Category table.
❑ The MemberId column in the FavCategory table is a foreign key linking to the MemberId column
in the MemberDetails table.
❑ The LocationId column in the Attendance table is a foreign key linking to the LocationId column
in the Location table.
❑ The MemberId column in the Attendance table is a foreign key linking to the MemberId column
in the MemberDetails table.
In an earlier Try It Out, you defined the relationship between the Attendance and Location tables. The
Location table is the primary table to which the Attendance table links via the LocationId column.
The Attendance table also links to the MemberDetails table, so you need to define that relationship
as well.
If you’ve already added the constraint in the earlier Try It Out, then don’t execute the code again or
you’ll receive an error. If you didn’t execute the code, then the SQL used in an earlier Try It Out to add
the constraint was as follows: