I corrected the connection test as you suggested, don't know how that slipped by.

Your second point is a good one, but eliminates the need for Class::DBI in that context. Class::DBI is not an end all be all for relationship integrity management. Class::DBI can however be used to manage relationships in situations where

The management of relationships has to be done at an application level vs. the database (somewhat database engine agnostic design)

The the database doesn't support more robust features, for which there are numerous examples and converting table format isn't an available solution because *insert subjective reason here*

"You said nothing about how DBI::Class handles queries with one or more JOIN"

Yes Class::DBI has many features and transparent SQL is one of them, but they are not within the context of an introduction. I plan to release a mid range tutorial after I complete my present project using Class::DBI. I am open for suggestions and or tidbits of what should be included in that node.