Database implementations/media info stuff?

[deebo]

Ive been studying the MP2 sources to get familiar with the way it works.

I'm extremely interested in shared database solutions so i've spent some time looking at the database solutions.

Currently it seems that all "plugins" call DatabaseFactory.CreateFromID() (MediaPortal.Database/Implementation)

And this always defaults to sqlite.

So, if i implement MediaPortal.Database/Implementation/MySql, will it be usable?

Is this a temporary solution only, will it be possible to define a implementation type for each "plugin" when the product nears release.



Also, bit off the topic, but id like some info on the media info stuff, ie if i want to implement a movie info scraper, what should it do? is there an interface for this already, like (IMediaInfoProvider -> MovieInfoProvider).

I'd guess it should implement something like List<MovieChoice>->IInfoChoice GetChoices(string movieName), SelectItem (IInfoChoice movieItem) etc

im just guessing here so any info welcome

[James]

Hi deebo,

I just made this change the other day. See Database task list: http://pms.team-mediaportal.com/inde...tive_project=1


Before this all plugins were selecting their own database. Now they are DatabaseFactory sets it. The plan way to have this configurable. Once I complete my work the existing Database implementations will become (sub)plugins. This will allow new database implementations (MySQL, etc) to be added via a plugins

However, I planned to only have one database that all plugins use (configurable). I was not planning to allow different databases per plugin?

Does anyone else feel they need to be able to have multiple databases? With different plugins using different ones?

[deebo]

that depends, i was just thinking that if everything is wrapped with databases, it might be a good choice to contain small things like share info, configurations etc in a local sqlite, but movie info, series info, tv info etc etc in a remote mysql database

does the core handle its own settings somehow are all are settings "plugins" like most of the mp2 architechture seems to suggest?

[James]

There is a Settings Manager, which will store the settings for all plugins and parts of MP-II. It uses xml files instead of a database.

[willow]

Standalone xml file doesn't sound like the best idea if you want to create a system that is as easy to manage as possible when there are multiple clients. Xml might still be good for storing the actual settings, but you might want to consider storing settings in an xml-file but storing the said xml in the db. That way your clients could easily synchronize settings (i.e. that xml-file) from central db.

[Lesther]

hi,

Sorry for my little knowledge, but i believe that if the system is centralized will allow in the future some cool features like monitor what on system is doing and the follow me feature like linuxmce. Again sorry if what I'm saying doesn't make sense...

[James]

Hi Lesther,

Its not a bad idea. At the moment user management is planned for a later release. Some thinking has already taken place, but it is still early days.

There is however always a problem with central storage. If the central server is not available the features that require it will not work. So I think some kind of synchronisation would be better.

/James

[James]

The database implementations are now loaded from the plugin space.

There are currently two implementations SQLite and SqlServer. New one can now be added via plugins.

[uggabugga]

Hi everyone,
Just wanted to make a little comment on this thred/matter
I would wish for the possibility(right after MPII has been installed) to be asked if I would like to use my local saved xml file or load one(and use/sync) from my "server".
But I think this should be divided into 2 kind of profiles. One "config" profile(remote control, codec selection if codec present, display settings setup. Settings that are/could be more HW related for the individual HTPC). This way when reinstalling Windows, one would apply this config file first.
The other kind of profile should be more of a "media" profile, that is more general in use(pictures, movies, series, skin choice and other media related.) One could dream to extend this to include Startup-delay time, skin, whether and so on, you get the picture.
Remember that this is just me "thinking out load here" so please do comment if there is something that I might not have given enough thought(probably is ) or you disagree on.

[PrplHaz4]

Originally Posted by James

There is however always a problem with central storage. If the central server is not available the features that require it will not work. So I think some kind of synchronisation would be better.

/James

I beleive the way that the MythTV project has done it is to use Master/Slave dbs, where your master acts as a publisher to each of the slaves/clients, so you get a situation where settings are basically cached locally, but always available through the master when anything changes or an updated configuration is loaded.

This also allows you to de-centralize storage, but have all media...etc accessible from everywhere...you'd just have to make sure to write some smart code that can work on/offline as needed, and handle a good deal of special events...