- May 13, 2007
- 418
- 37
- Home Country
- United Kingdom
As for database location I had another thought whilst trying some sutff on the weekend. Basically I want to have a master MP install that I controls all the download of program info and does the scanning, etc...
I then use some scripts to mirror this info out to the other MP machines; this seems as good a solution as a central DB for Tvseries info + adds a bit of DR
My problem here is that all the info for the plugin is stored in the same database (correct me if I am wrong). What would like to see is:
1. A TVSeriesConfig.xml file locally on each machine that holds all the plugin setting, ie, lanuage, auto scan folder, down settings, etc....
2. A TVSeries database that holds just info that has been collected from a scan, ie, episde guides, file location, file tyrpe, etc... all the stuff ont he first screen.
3. A TVwatched.xml or DB. This holds a flag to say if a show has been viewed. Maybe you could do this by replacing the watched field in the current DB to a link to a new db that just has a primary key index based on the show unique key and a watched field (don't know how this will effect speed).
Waht this will give is:
TVSeriesConfig.xml = NOT copied around. Left unique on each machine.
TVSeries.db = COPIED from Master to all slaves using a directory watcher for file change, or view a scedulled task every x minutes.
TVwatched.xml = Conditionally copied. So mayeb the Lounge, kitchen and Master bedroom are kept in sync. but the other bedrooms have a unique watched file.
Disk space is not an issue on the local machines, but speed is, so maybe this posses a simpler soltution than trying to do a central DB solution.
I then use some scripts to mirror this info out to the other MP machines; this seems as good a solution as a central DB for Tvseries info + adds a bit of DR
My problem here is that all the info for the plugin is stored in the same database (correct me if I am wrong). What would like to see is:
1. A TVSeriesConfig.xml file locally on each machine that holds all the plugin setting, ie, lanuage, auto scan folder, down settings, etc....
2. A TVSeries database that holds just info that has been collected from a scan, ie, episde guides, file location, file tyrpe, etc... all the stuff ont he first screen.
3. A TVwatched.xml or DB. This holds a flag to say if a show has been viewed. Maybe you could do this by replacing the watched field in the current DB to a link to a new db that just has a primary key index based on the show unique key and a watched field (don't know how this will effect speed).
Waht this will give is:
TVSeriesConfig.xml = NOT copied around. Left unique on each machine.
TVSeries.db = COPIED from Master to all slaves using a directory watcher for file change, or view a scedulled task every x minutes.
TVwatched.xml = Conditionally copied. So mayeb the Lounge, kitchen and Master bedroom are kept in sync. but the other bedrooms have a unique watched file.
Disk space is not an issue on the local machines, but speed is, so maybe this posses a simpler soltution than trying to do a central DB solution.