Page 1 of 1
Unification of Media Data Base
Posted: 07 Sep 2017, 12:45
by Everbrave
MrMC has multiple Media-DB:
- local XBMC
- one for each Plex Server
- one for each Emby Server
It would be nice to merge all these in one Super-DB while eliminating multiple entries (OR-conjunction) in the file list but keeping the link to each individual DB.
When the root of one DB is not found. e.g. one Plex Server is off, MrMC would refer to the alternative
The B-tree structure suggests itself here, but, of course, there are other possibilities.
Re: Unification of Media Data Base
Posted: 07 Sep 2017, 13:28
by davilla
Everbrave wrote: 07 Sep 2017, 12:45
MrMC has multiple Media-DB:
- local XBMC
- one for each Plex Server
- one for each Emby Server
It would be nice to merge all these in one Super-DB while eliminating multiple entries (OR-conjunction) in the file list but keeping the link to each individual DB.
When the root of one DB is not found. e.g. one Plex Server is off, MrMC would refer to the alternative
The B-tree structure suggests itself here, but, of course, there are other possibilities.
Not going to happen

It's just too complex to handle. Plus both Plex and Emby clients do not have any interaction with the sqlite/
mysql databases. There's not even a database involved with plex/emby native clients. Emby does 1st level caching, that will get added with Plex in a future release.
Most users run sqlite/
mysql OR plex OR emby. Not a mix of all. We do that here for testing.
Re: Unification of Media Data Base
Posted: 07 Sep 2017, 15:39
by Everbrave
davilla wrote: 07 Sep 2017, 13:28
Everbrave wrote: 07 Sep 2017, 12:45
MrMC has multiple Media-DB:
- local XBMC
- one for each Plex Server
- one for each Emby Server
It would be nice to merge all these in one Super-DB while eliminating multiple entries (OR-conjunction) in the file list but keeping the link to each individual DB.
When the root of one DB is not found. e.g. one Plex Server is off, MrMC would refer to the alternative
The B-tree structure suggests itself here, but, of course, there are other possibilities.
Not going to happen

It's just too complex to handle. Plus both Plex and Emby clients do not have any interaction with the sqlite/
mysql databases. There's not even a database involved with plex/emby native clients. Emby does 1st level caching, that will get added with Plex in a future release.
Most users run sqlite/
mysql OR plex OR emby. Not a mix of all. We do that here for testing.
Sad

but can we do?
I know/own one player which can do that; at least its own DB (Helper running on a Mac) with Plex; Squire.
http://squireapp.com
You might want to take a look at it if you wish; free for Mac, not expensive for iOS/tvOS.
BTW, the developer, Fernando, is a very nice guy from Spain, and the UI is very nice too.