@silver-sun Done, done, and partially done.
I'm on Ubuntu and have already cracked it open with DB Browser. 'It' being the .db file, I didn't know the .db.bak was a backup I could also check.
I know some rudimentary SQL and how databases work, but I still don't know how to interpret the data. I've found the playlists table and it's full of the plaintext names of the playlists, but not the songs or any data about the playlist contents. There's also playlist_items with columns like playlist, collection_id, and playlist_url, which I assume has to mean something but all the columns are integers bereft of context (playlist_url is entirely full of NULL cells). Does anyone know how to interpret the data in the database? Is there any documentation on how the database is meant to work?
Update: Reading through the rest of the columns in playlist_url it seems like there are supposed to be plaintext cells with song titles, artists, albums, etc. They're all empty. At first I figured this meant the data was destroyed, but I copied the .db file I've been using with new playlists so I could see what the data was supposed to look like. Just like in the old database, every column which should hold the titles and such was empty. The only data that differed consistently (to a point) row to row was collection_id. Does collection_id represent a unique identifier to a song? How does Strawberry actually interpret the playlist_items to get data about the items in playlists out?