>> EAV (Entity Attribute Value) tables—use a specialist product intended for handling such schema-less data instead. > What if you have to use the data in some

>> EAV (Entity Attribute Value) tables—use a specialist product intended for handling such schema-less data instead. > What if you have to use the data in some complex join-heavy query? Make a copy of the data needed in the relational database and hope that the data doesn't get unsynchronised? No, he's saying that schema-less, arbitrarily-extended information has no business in a relational system at all.