Tukukkk

I have an iOS app where users can create Sessions. A Session mainly consists of an optional audio recording (saved locally) and some stats related to the session.

Users can also:

• Create folders (that are also created on the device)


• Rename the audio file


• Rename folders


• Move audio file to a different folder.


• Move folder to a different folder.

Right now, when a session is completed, I store it in a database in a format similar to:

    var id: String = ""

    var duration: Double = 0

    var filename: String?

    var path: String = ""

    var isDirectory: Bool = false

    var data: SessionStats?

It seems that the current database design is overly coupled to the file system. The problem is when a folder name changes or is moved, I have to update all path fields in the database for sessions that are within that folder. If a folder is deleted, I also have to find all children of that folder to remove them from the database. It also seems like there may be cases where the file system and database get out of sync (if an update failed for some reason).

Is there a better structure for this? Right now I'm using realm for the database, but I'm open to all solutions.