I think your problem is a great fit for SQLite. If you don't want to maintain the SQL syntax between storing and retrieving your date, you could look into KeyValueStore2 and let it handle all the details for you (underneath, it uses SQLite). Plus, your stored data is encrypted (if that is a requirement). If you do not need to store the data between program executions, you could still use SQLite, but have it create in-memory database(s) only (without writing to disk). Since the source is available for KeyValueStore2, you could modify it to use a in-memory database.
If you go that far to write your own read write methods to serialize data to store and to retrieve your data and de-serialize it, why not just stick with KeyValueStore2? I do agree though that if writing is not needed, a class, declared globally, should suffice.
If you go that far to write your own read write methods to serialize data to store and to retrieve your data and de-serialize it, why not just stick with KeyValueStore2? I do agree though that if writing is not needed, a class, declared globally, should suffice.
because often u have a class with functionality & data and typically you will save/load this by a own Sub or the easy way as Object to File.
b4xserializator is also a cool way for transport a object (or object list) via network from app to app.
If you go that far to write your own read write methods to serialize data to store and to retrieve your data and de-serialize it, why not just stick with KeyValueStore2? I do agree though that if writing is not needed, a class, declared globally, should suffice.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.