2014-07-29, 19:09
Link to folder with all info and files: http://1drv.ms/1IO2Jn3
Following suggestion I have opened a new thread to discuss the DB.
The original point was to have the possibility of using different DB servers as shared library among different XBMC.
In addition to optimize how the DB is managed (real transactions, one connection to db non thousands, etc..).
This lead to me thinking a new, simple but very flexible db structure to host all possible contents.
I will post the project and model online. I'm using the best (and free) data modeler:
http://www.casestudio.com/enu/default.aspx
TOAD Data Modeler
Here is the summary of first draft of the logical of the new db:
Ok here is the first part of the model:
http://1drv.ms/1Aj0KCz
The movies table still miss a lot of fields and I have not added yet the season-series, also there is a separate are for the TV-EPG
but the core is there...
Some of the key concepts:
1) there is a file table that includes all files independently from what they are
2) files are grouped in libraries
3) users can filter libraries
4) an asset is composed by different files (i.e. multipart movie)
5) assets can be: movie, episode, pictures, music, thumbnail, module, etc...
6) each specific asset does have it's own set of specific properties
7) rating/stars are linked to assets
8) series/seasons are a grouping of assets
9) watched is linked to assets
10) there is a path table where we can store any path format and the format is speficied in path/type. In this way we can have Linux based path/samba/URI etc... also path substitution becomes very easy
CRC32 is used to identify univokely a file
I think this base structure takes in account everything I've read so far in the different posts GSOC and in the code.
For pictures I've already added the EXIF information and we can easily add an Album level as a grouping of pictures like a season/series is a grouping of episodes.
For movies Sets are just a grouping of movies.
Following suggestion I have opened a new thread to discuss the DB.
The original point was to have the possibility of using different DB servers as shared library among different XBMC.
In addition to optimize how the DB is managed (real transactions, one connection to db non thousands, etc..).
This lead to me thinking a new, simple but very flexible db structure to host all possible contents.
I will post the project and model online. I'm using the best (and free) data modeler:
http://www.casestudio.com/enu/default.aspx
TOAD Data Modeler
Here is the summary of first draft of the logical of the new db:
Ok here is the first part of the model:
http://1drv.ms/1Aj0KCz
The movies table still miss a lot of fields and I have not added yet the season-series, also there is a separate are for the TV-EPG
but the core is there...
Some of the key concepts:
1) there is a file table that includes all files independently from what they are
2) files are grouped in libraries
3) users can filter libraries
4) an asset is composed by different files (i.e. multipart movie)
5) assets can be: movie, episode, pictures, music, thumbnail, module, etc...
6) each specific asset does have it's own set of specific properties
7) rating/stars are linked to assets
8) series/seasons are a grouping of assets
9) watched is linked to assets
10) there is a path table where we can store any path format and the format is speficied in path/type. In this way we can have Linux based path/samba/URI etc... also path substitution becomes very easy
CRC32 is used to identify univokely a file
I think this base structure takes in account everything I've read so far in the different posts GSOC and in the code.
For pictures I've already added the EXIF information and we can easily add an Album level as a grouping of pictures like a season/series is a grouping of episodes.
For movies Sets are just a grouping of movies.