生成复杂DB（EAV）的单元测试数据

I'm working with a legacy application that makes some use of the well-known/dreaded data modeling pattern known as EAV. This has made choosing a data generation strategy to use during unit testing of the DAL difficult. Why? Because, in addition to the normal Fk/Pk constraints between tables (which we are using when possible), there are additional relationships/constraints that only the application layer is aware of and enforces. I'm working with a legacy application that make