1) add column "is_folder" (or something similar) to crates/playlists table and forbid to add tracks to such a crate/playlist
2) add new table "crate_folders"
What do you think is better? I think first aproach can be sometimes faster as We can avoid some JOINs, but the table can be significantly bigger (I don't have idea how many crates people have...). And make the work with it easier. I don't like idea of having playlist which can't have songs added to...
In right-click menu on folder there will be option "Add folder".
Should folders display songs of their children or no tracks?
Ok. So I'll add folders for both of them.
I see two ways how to put this into database:
1) add column "is_folder" (or something similar) to crates/playlists table and forbid to add tracks to such a crate/playlist
2) add new table "crate_folders"
What do you think is better? I think first aproach can be sometimes faster as We can avoid some JOINs, but the table can be significantly bigger (I don't have idea how many crates people have...). And make the work with it easier. I don't like idea of having playlist which can't have songs added to...
In right-click menu on folder there will be option "Add folder".
Should folders display songs of their children or no tracks?