Hi,
The way I see the integration between monosqlite and arrayMaker is the following:
1: A GameObject will be created solely to host the arrayLists of the dataset. so you'll have one arrayList for each column of the table you are querying, I think it will be a very good and flexible start.
2: The opposite could be true, I think I could take a gameObject, analyze its arrays and build/update the corresponding tables and data back to monoSqlite. So effectivly, you could load AND save datasets to monosqlite very easily.
2: The big issue I am having theoretically with monosqlite at the moment is that it doesn't support vectors, bool, etc etc. So a big part of the job will be to write a proxy that will allow users to store a vector3 for example without caring about how it's actually defined in the database. I think this will greatly increase the range of possibilities for monosqlite.
This is all very theoretical, I have yet to dive into all this properly.
bye,
Jean