I have to agree with most of what's been said here. As a general rule, EAV is much more costly in development time (especially for enhancements), storage, and performance than a proper relational model - there are exceptions to this general rule (for example if almost everything is extremely sparse you may get a storage saving from EAV, provided you avoid having to encode the datatype with each value) but these are very rare indeed.