My app has about 10 different forms, each with an average of 10 text fields where users will enter lengthy answers to questions, some being many paragraphs long, others one word answers. It is also a place where users will come back and modify their answers frequently. I have set up the app to save each rendition of the change as a new thing, so if they make a small adjustment like a comma addition to text, Bubble will save that full text box of data as a new thing.
The benefit of this is there is audit trial, and timeline of how data was manipulated over time. This is somewhat important but its this feature that will multiple the ‘things’ in my database many many times over.
For example, if a user without any edits saves their data, that’s a 100 new things added to the database. Fine. However, if they were to on average make 200 changes per each of the 100 fields, that’s now 20,000 new things to store per project. There might be 100s of projects in the distant future, so millions of ‘things’ to store. And this doesn’t take into account other store of data that the app will have for other features which I"m planning.
I’m sure most will simply suggest ‘modifying’ a thing when a user needs to go back in and make a change instead of saving it as a new entry, which is fine. But if I do this, how will keep a track of data that was changed over time, for a particular field? Is there a way for the app to only record a new ‘thing’ where a major change has taken place which I can specify, perhaps X characters added etc?