Beginning SQL
Beginning SQL Beginning SQL
Chapter 3 106 You should see the following results: Category MemberId Thriller 5 Thriller 10 Thriller 12 Romance 1 Romance 14 Horror 10 Horror 11 Horror 13 War 6 War 1 War 11 War 12 Sci-fi 4 Sci-fi 11 Sci-fi 13 Historical 10 Historical 12 Historical 14 Comedy 6 Comedy 4 Comedy 12 Because three new records appear in the FavCategory table with a matching record in the Category table, the results appear in the resulting join. The next stage joins the MemberDetails table to the current results set: SELECT Category.Category, MemberDetails.FirstName, MemberDetails.LastName FROM FavCategory INNER JOIN Category ON FavCategory.CategoryId = Category.CategoryId INNER JOIN MemberDetails ON FavCategory.MemberId = MemberDetails.MemberId ORDER BY MemberDetails.LastName, MemberDetails.FirstName;
- Page 200: Chapter 3 2. Add a WHERE clause to
- Page 204: Chapter 3 Executing this SQL provid
- Page 208: Chapter 3 84 FullName First name is
- Page 212: Chapter 3 86 FullName First name is
- Page 216: Chapter 3 Even though DateOfBirth i
- Page 220: Chapter 3 Member Name The member is
- Page 224: Chapter 3 92 The preceding SQL prod
- Page 228: Chapter 3 94 ❑ Category ❑ FavCa
- Page 232: Chapter 3 96 You’re one step furt
- Page 236: Chapter 3 98 FirstName LastName Cat
- Page 240: Chapter 3 This time, you achieve mo
- Page 244: Chapter 3 SQL Is Set-Based 102 You
- Page 248: Chapter 3 104 Category MemberId Thr
- Page 254: Remember to add brackets around the
- Page 258: surprisingly, the MemberDetails tab
- Page 262: LocationId 2 2 2 2 1 1 1 Figure 3-6
- Page 266: includes that record. You should al
- Page 270: FirstName LastName DateOfBirth Jenn
- Page 274: 4 Advanced Database Design This cha
- Page 278: Date of Date Meeting Did Member Nam
- Page 282: Now the tables are in second normal
- Page 286: After changing the database so that
- Page 290: IBM’s DB2 doesn’t allow you to
- Page 294: The following code creates a new ta
- Page 298: If you’re using DB2, the code is
Chapter 3<br />
106<br />
You should see the following results:<br />
Category MemberId<br />
Thriller 5<br />
Thriller 10<br />
Thriller 12<br />
Romance 1<br />
Romance 14<br />
Horror 10<br />
Horror 11<br />
Horror 13<br />
War 6<br />
War 1<br />
War 11<br />
War 12<br />
Sci-fi 4<br />
Sci-fi 11<br />
Sci-fi 13<br />
Historical 10<br />
Historical 12<br />
Historical 14<br />
Comedy 6<br />
Comedy 4<br />
Comedy 12<br />
Because three new records appear in the FavCategory table with a matching record in the Category<br />
table, the results appear in the resulting join.<br />
The next stage joins the MemberDetails table to the current results set:<br />
SELECT Category.Category, MemberDetails.FirstName, MemberDetails.LastName<br />
FROM FavCategory INNER JOIN Category<br />
ON FavCategory.CategoryId = Category.CategoryId<br />
INNER JOIN MemberDetails<br />
ON FavCategory.MemberId = MemberDetails.MemberId<br />
ORDER BY MemberDetails.LastName, MemberDetails.FirstName;