As my app grows I’m thinking ahead to a much larger database. My current thought process is to store information older than a year in an external database. I’m not looking for users to be able to access this database, but have it as a backup that we can access on user’s request so I can auto archive information after a year and remove it from my bubble database.
Is there a better solution to this or, if this is the best plan, any recommendations on what to use and how to set it up?
My app had a ‘glitch’ earlier in the year that showed someone else’s information to the wrong person. Privacy settings are in place but ultimately the particular data has to be visible to someone not logged in so is public. It was all set to show only ‘current page thing’ and other constraints etc etc and when I spoke to Bubble they said it was just a random glitch due to a string of unlikely events that caused it, and that it’s unlikely to happen again…however since then I’ve been trying to keep the database as lean as possible as it was ‘old’ data that had been shared with the wrong person and obviously my user wasn’t happy
Ok thanks for this @georgecollier. So in my case it’s app messages in the database, can I create a backend workflow that would show a message that is set to private to a non logged in user?
Sure, just send some magic link to a user, the ID of which is saved to the Message, and when the page is loaded, make a call to a backend workflow that finds the Message with that ID and returns the fields to the front-end using the app connector
