2019-11-12, 21:42
Most people prefer having .nfo's stored to their media. That's why I was suggesting an array.
With an array I can update the Kodi centralized .nfo and the one next to the media. If I only can update the centralized ones, the ones of the folders will stay untouched. On a crashed system people will rescan their storage folders and the edited values are lost.
Emby also has a own local storage. .nfo's are only used as "copy". If my server main SDD will die on some day -> I don't care, the .nfo's are still next to the media.
But anyway, I'm not in the position or having the know-how to correctly built a database scheme. Just a skinner that has learned Python by mistake. I'm sure you will find a correct solution. It's your playground and you have more experience with it than I'll ever have
With an array I can update the Kodi centralized .nfo and the one next to the media. If I only can update the centralized ones, the ones of the folders will stay untouched. On a crashed system people will rescan their storage folders and the edited values are lost.
Emby also has a own local storage. .nfo's are only used as "copy". If my server main SDD will die on some day -> I don't care, the .nfo's are still next to the media.
But anyway, I'm not in the position or having the know-how to correctly built a database scheme. Just a skinner that has learned Python by mistake. I'm sure you will find a correct solution. It's your playground and you have more experience with it than I'll ever have
