Hi everyone,
I have data type “play” that is created every time a user plays a piece of audio. I have it as a data type to provide date-based analytics to the creator of the piece of audio. Let’s say the user decides to delete that piece of audio. Should I also delete all the “play” data types or just let them be? There could be thousands of these.
The “Play” data type only has field 3 fields, including one that refers to the “original-piece-of-audio”
Your input is appreciated!
Is it just for counting? It would be less WU consuming to create a field and let run a workflow to add +1 to the previews value. For analytics your idea is no problem. Just make a field (list) in the “Audio” where you add the “Play” to a list. Having millions of rows is no problem: Millions of rows can bubble search features work on that size of a dataset? - Need help / Database - Bubble Forum
it would be better to soft-delete, using a yes/no “isDeleted” field. Then the Plays don’t get orphaned with no reference of what audio file they were
It also depends what do you want to happen when the audio is deleted, do you have any RGs searching for Plays? Would you want to hide the ones that got their source audio file deleted?
I’m not sure I understand you completely.
Are you suggesting to add an “isDeleted” field for the “play” data type? And then when the audio is deleted by the user, I should modify each one of them to have “isDeleted” as yes?
