For my bachelor thesis I have to build a reseach database which has to meet the requirement of provenance. In the present case it means that among other things I have to store the results of my queries and the query itself in the database.
The problem I encounter is the fact that I can get results which structure is not known before. I can get scalar result, e.g. an average value, I can get an n-tuple as a result or even tables as a result of a table function. The user is allowed to perform any operation on the raw data and the result has to be stored in the database.
My thesis tutor suggested me to use the EAV schema. I have read a couple of posts on DBA and have seen that this can get extremely complicated, especially when you have something like nested datatypes in the result (e.g. A graph as a result has points, a point has X- and Y- coordinates, the coordinates have float-values. I implemented an EAV schema in MySQL and have seen the complexity to store this). Nearly everyone disadvised to use EAV on DBA.
Is there a useful alternative to this EAV schema in my case? I have read some papers about some approaches with NoSQL databases but the problem is that I have to use MySQL because the institution which takes care on my thesis uses MySQL for their curated research databases.