qWave

uh. Oh. 8 hours. Uh. Oops.
Yeah uh I wanted to have a frontend utility to have all of my devlogs not just be a bunch of code spewed out and then I decided I needed to do all the config stuff and spend way too long overthinking exactly how it will work… BUT GOOD NEWS next devlog I’ll be able to actually start the app and start moving some data about! First orders of business will probably be to figure out how to transcode files (jobs) then serve them to clients with direct Song ID requests, then I can start organizing them. I will uh. Try to make that Not 8 hours this time.

iiiiiii am in Pain trying to learn databases and SQLAlchemy at the same time, so this has taken far longer than it should have to set up the “model” files (basically a guide for the software to translate python objects later into SQL)

Set up a neat diagram for the tables to hopefully let me understand them better because I may be in a bit over my head, this may or may not change over time, but you can see it at https://dbdiagram.io/d/qwave-db-setup-695a456039fa3db27b0c1f73

(very minor mistake (you can’t change devlog attachments) in playlist_tracks there should not be a connection between playlist_id and track_id)