Hey, Jeff I only read the first and last pages so I hope this hasn't been mentioned already. My company is a major developer for users of the DotNetNuke content management system which was originally developed as an open source project a dozen years ago.

Probably due to lack of foresight as to how big the DotNetNuke platform would become, some of the major components of the DNN schema implemented the EAV model. Now for the "regular" folks who just want to add "Shirt Size" or "Dog Breed" attributes to their system's user profile data this is really cool. They can add whatever categories upon categories with whatever attributes they want in any language. They can even create master lists (like states in OZ vs no states in NZ) or lists of bird calls by continent or whatever they can think of.

But almost all of my interface with DNN is through SSMS and customization of the database. This is my daily job. And there's tons to like about the DNN platform, but having to deal with these throwback EAV tables often makes me want to throw a shoe at somebody. 😛