Data Storage

[HenryGeorgist]

Currently the Datastorage is part of the View Model. In general data storage is a model concern. I would like to open a discussion about data storage being migrated into the model.

[Brennan1994]

the SQL lite database adds a lot of complexity I don't love. I'd be interested in alternatives. I don't feel good about learning and reimplementing database manager into the model. I'm not absolutely opposed, but It give me bad feels.

@HenryGeorgist could you lay out and briefly describe some alternatives?

[HenryGeorgist]

no requirement says we shall use sqlite. I do not propose migration of the previous datamanager.

The data is roughly some groupings of paired data and paired data uncertain with sparse attributes. I propose we store it in something simple, xml or json for instance.

we can add an interface for data storage something like "public void Write(string writecontext)" where write context could represent a file path or an s3 key value pair. And "public void Read(string readcontext)" which we can change out our data model at any later date.

[rnugent3]

Is this something we'd need to do for product to be available for use in December?

[HenryGeorgist]

it depends on how we wish to proceed. we should talk it through. If we want a product by December, yes, starting fresh with a new datastore would be much simpler than trying to migrate the current database out of the VM. This decision impacts migration to the existing UI, so it should be something we discuss sufficently.

[rnugent3]

Thanks, Will. I'll add this to the agenda for our chat later this week.

[rnugent3]

we have been moving more and more data storage responsibilities to the model. I don't expect to have all data storage responsibilities owned by the model for 2.0, but for releases thereafter we can pursue 100% of relevant data storage owned by the model.