Ch7 Misleading FK Constraint name

[kosjir]

In Chapter 7. Physical Model Implementation, in the text following after Figure 7-5 Messaging model for reference is ALTER TABLE statement to implement FK in the table MessagingUser; relationship between MessagingUser and AttendeeType.
ALTER TABLE Attendees.MessagingUser
ADD CONSTRAINT FKMessagingUser$IsSent$Messages_Message
FOREIGN KEY (AttendeeType)
REFERENCES Attendees.AttendeeType(AttendeeType)
ON UPDATE CASCADE
ON DELETE NO ACTION;
The name of the CONSTRAINT FKMessagingUser$IsSent$Messages_Message is however a bit misleading. It suggests rather (one of) the relationships between tables MessagingUser and Message (in the Figure „is sent“) but in reality the „categorizes“ relationship is being established.