Consider moving the data storage to eg. sqlite #3
Labels
Milestone
Comments
Maybe some comments (as there was interest by some party to work on it).
|
Oh, and
|
One more note, as I was just thinking about it. For a start we could only move the per-sheet data storage over into sqlite. The questionnaire/survey information could still stay in the current format. That really means that we may only need a simple (sheet, id, key, value) storage system that supports values of different data types. |
This has now happened. It just dumps json seralised objects into the database. One for the questionnaire and one for each "sheet". |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the data is stored by simply pickeling it. This works really great, but my guess is that this is a limitation in some use cases (you need to create a new project, etc. every time).
A first step to make SDAPS more flexible in this regard would be to move to an SQLite based storage per project. Once that works, one could consider using only one database for multiple projects.
Doing this could make it easier/possible to automatically sort scanned data into the correct project.
The text was updated successfully, but these errors were encountered: