In the RDBMS community, EAV is antipattern. For the “flexible flexibility” obtained using EAV, SQL is required for data recovery, since records / objects are much more complex. You also benefit from the fact that you cannot use any available data integrity tools (foreign keys, control restrictions, etc.). Over time, this project collapses under its own weight.
If you have a use case when data elements are part of a supertype / subtype relationship, but they do not change much, then model the tables according to your needs:
1.) Table = . , .
2.) = . , , .
3.) = 1 . , , NULL. , , /.
3, .
EAV, XML RDBMS, EAV ( ). EAV, RDBMS - , . Document/NoSQL/Key-Value, MongoDB, Cassandra .. RDBMS, EAV, , .
, , , , / ..