2013-05-01, 19:14
As I have a fairly large library with many devices in the house I prefer to use MySQL on a NAS, quite a common thing.
As the library is large I prefer to do my updates on my desktop MySQL installation and have the NAS operating as a slave. However, the slave keeps falling over because of updates with shows watched etc.
There are, of course, multiple solutions to this. I currently run the slave user with minimum privileges (DELETE, EXECUTE, SELECT, TRIGGER) but this removes bookmarks and watched statuses.
It would be nice if there could be a split of where reads and writes connect (as an option, of course)
It would be even nicer if we could have profiles (either within XBMC, or as user connections) where functional writes for watched statuses etc can be stored in user specific tables, rather than centrally. While I have played with doing this myself in the past, this doesn't help others and, of course, means having to track database changes.
As the library is large I prefer to do my updates on my desktop MySQL installation and have the NAS operating as a slave. However, the slave keeps falling over because of updates with shows watched etc.
There are, of course, multiple solutions to this. I currently run the slave user with minimum privileges (DELETE, EXECUTE, SELECT, TRIGGER) but this removes bookmarks and watched statuses.
It would be nice if there could be a split of where reads and writes connect (as an option, of course)
It would be even nicer if we could have profiles (either within XBMC, or as user connections) where functional writes for watched statuses etc can be stored in user specific tables, rather than centrally. While I have played with doing this myself in the past, this doesn't help others and, of course, means having to track database changes.