Reply to thread

Message

<blockquote data-quote="Gerke Grashuis" data-source="post: 869317" data-attributes="member: 124770">This is how I use the centralized database:My htpc rig is dedicated for viewing movies only.It only gets fired up when I want to view a movie. That involves firing up my lcd television, receiver and htpc.Takes quite some time for say adding a movie to my Moving Pictures database.That is why I moved all the MP databases to a central location on my NAS (which in fact, downloads and stores movie content too)My laptop, which gets used every evening, is equipped with MP and Moving Pictures too and points to the same central MP databases.Now I am able to update the Moving Pictures database whenever I want and without firing up the htpc rig.It also gives me the ability of having a quick look at the content, to see if it stands up to my quality expectations, before adding to the database.Concurrent use of the database(s) is, again, not supported.&nbsp;Now, about the wiki describing the setup of a centralized database, I shall update that as soon time permits.Above that, I will add a subject on a way how to prohibit concurrent use to prevent database corruption by mistake.Maybe with some code examples too.Again, don't use it myself so it has to be build and tested.</blockquote>

[QUOTE="Gerke Grashuis, post: 869317, member: 124770"] This is how I use the centralized database: My htpc rig is dedicated for viewing movies only. It only gets fired up when I want to view a movie. That involves firing up my lcd television, receiver and htpc. Takes quite some time for say adding a movie to my Moving Pictures database. That is why I moved all the MP databases to a central location on my NAS (which in fact, downloads and stores movie content too) My laptop, which gets used every evening, is equipped with MP and Moving Pictures too and points to the same central MP databases. Now I am able to update the Moving Pictures database whenever I want and without firing up the htpc rig. It also gives me the ability of having a quick look at the content, to see if it stands up to my quality expectations, before adding to the database. Concurrent use of the database(s) is, again, not supported. Now, about the wiki describing the setup of a centralized database, I shall update that as soon time permits. Above that, I will add a subject on a way how to prohibit concurrent use to prevent database corruption by mistake. Maybe with some code examples too. Again, don't use it myself so it has to be build and tested. [/QUOTE]

Verification