Open benbowler opened 9 years ago
There is an artist_id
field referring to the artists
table. No release field for tracks, but I'm open to extending the model. I wonder if it would be better to add a generic metadata field instead of adding new fields one column at a time to the schema?
I was using a branch which didn't have artist for some reason.
How would you suggest including meta data? a meta data and a join table for a one to many relation ship?
It could either be a separate trackID/key/value table that gets joined, or a single metadata field that holds a serialized JSON object. I don't have a preference either way.
There currently aren't artist or release fields in the system. Was this deliberate? If I added support of these fields would you accept a pull request?