Content
View differences
Updated by Eric Schubert over 4 years ago
### Issue
Currently we save all snapshots as BASE64 within the JSON of a viewpoint in the DB. Meanwhile we also store the image as a file as an attachment. So we save the data twice.
Saving the snapshot in the DB looks wrong and thus shall be removed for the following reasons:
* It increases the DB size
* It currently increases the payload of every viewpoint request unnecessarily
* It does not get used anywhere
* It is not part of the BCF API schema for viewpoints
### Motivation
* decrease significantly the size of data in rest of bcf viewpoints
Currently we save all snapshots as BASE64 within the JSON of a viewpoint in the DB. Meanwhile we also store the image as a file as an attachment. So we save the data twice.
Saving the snapshot in the DB looks wrong and thus shall be removed for the following reasons:
* It increases the DB size
* It currently increases the payload of every viewpoint request unnecessarily
* It does not get used anywhere
* It is not part of the BCF API schema for viewpoints
### Motivation
* decrease significantly the size of data in rest of bcf viewpoints