Storage Space

[sirgolan]

I've been trying to come up with a better way to persist MV3D state info. Basically, I need a solution that meets the following:

Synchronous when saving data

Transactional

Extremely Fast when saving data

Maintains data consistency

Supports queries

Externally available (i.e. you can view/modify/query the data outside of MV3D)

Low CPU overhead

Comments

[sirgolan]

How about this? Same set-up, except a local sqlite store is always written to. It can be replicated out to a remote store in real time if desired. That way, you could get synchronous feedback if the transaction was successful. This would require not using normal auto-incrementing integer primary keys in the tables, but I think that could still be ok.