Not really, as this is not a good relational model, but a simple EAV (entity attribute value) approach. You don't need a database for this, it's the same as "record" files in the 1960s.
There is no data integrity, no structure to query and certainly not safe data. If you have one misbehaving application accessing this database, it's all over.
EAV is the right approach for very rare cases, as an addition to a normalized relational model of entities, i.e. if full dynamic attributes are required without changes to the database schema.
_________________ JAVA PERSISTENCE WITH HIBERNATE http://jpwh.org Get the book, training, and consulting for your Hibernate team.
|