Does anyone know where can I find a discussion on the three different O/R mapping strategies:

table-per-class-hierarchy
table-per-subclass (normalized mapping)
table-per-concrete-class

I understand the concepts but am looking for a list of pro's and cons and information on why the table-per-class-hierarchy is the recommended choice.

The database schema that I am working with seems to fit best with the table per subclass strategy and I am wonder what issues/concerns that I might encounter by taking that approach.

Don't know of a specific discussion.

The normal fear associated with the table-per-subclass approach is the possibility for large numbers of joins that can result during loads and queries.

As steeve said, it deals with the king of query you'll need... all depends on volumetry...

of course i wanted to say
As steeve said, it deals with the kinD of query you'll need... all depends on volumetry...

;)