Hey guys, I am about to embark on a project to convert an old database made in a different system (filemaker) to bubble. It is a music database which contains Songs. Each song contains a list of musicians involved on that song, their role and their share of the song. So three main tables 1) Songs 2) Musicians 3) Roles. The shares(%) are currently stored on the JOIN TABLE that links the writers to the songs. So for example the join table looks something like this:
(so in this example SongID “1” would have two musicians associated with it. SongID “2” only has one musicians associated with it)
The portal (“repeating group”) then shows the relevant details based on when the current SongID matches the SongIDs on the join table. Hope that makes sense.
My question is what is the best way to achieve this in Bubble? Do i continue to use this “Join Table” approach or does bubble hope I do things differently? Ie no uniqueID numbers and no join tables - just connected fields and the use of ‘list’ fields? I’ve read lots of posts on this forum but i am still not clear what is the best approach. For example, if i use lists, then where would I store the “Share%” data? or maybe i also want to add a “notes” field, which may contain info specific to that musician on that particular song.
The secondary question is one of compatibility… i’m going to have to, at some point, import all the data from my current system to the new bubble one. (over 1000 songs). If i switch to a non join-table approach would importing from old database then become a major headache? Will it be easiest to simply copy the structure & data used on previous database including all the unique IDs?
I’ll really appreciate any help given.
