Reply to thread

Message

<blockquote data-quote="fforde" data-source="post: 295669" data-attributes="member: 52082">Well I don't want to get into a debate about it, but I still have not heard a single argument for why moving to a more robust database server is a good idea for MP. Transactional databases like SQL Server or MySQL offer many many advantages over an embedded DB like SQLite. But the only one I can think of that applies to MP is concurrent access. But you are wrong, the logic for this is not already in place, and whichever way you implement a multi-seat system, you are not reinventing the wheel, regardless of whether or not you use a client/server setup. How does one box know data was changed by another box? How do you prevent multiple boxes modifying similar data at the same time? How do you manage individual settings on a box by box basis? How do you handle video or music files stored on a central server? Do all the systems need to map their network drives the exact same way? Is it ok to place this requirement on the user? Will a server stream the content? These are the hard questions that have to be answered, regardless of how you implement a multi-seat system. Having all the boxes connect directly to a central database doesn't get rid of any of these problems. I am not saying a client/server setup would immediately solve these problems either, but I am saying that it would reduce the system requirements and complexity from the users point of view.So what advantages does using a enterprise level database solution bring us? Concurrent access can be done other ways so that is out. Sure SQL Server or MySQL is going to outperform SQLite, but the database is not the performance bottleneck for MediaPortal...</blockquote>

[QUOTE="fforde, post: 295669, member: 52082"] Well I don't want to get into a debate about it, but I still have not heard a single argument for why moving to a more robust database server is a good idea for MP. Transactional databases like SQL Server or MySQL offer many many advantages over an embedded DB like SQLite. But the only one I can think of that applies to MP is concurrent access. But you are wrong, the logic for this is not already in place, and whichever way you implement a multi-seat system, you are [b]not[/b] reinventing the wheel, regardless of whether or not you use a client/server setup. How does one box know data was changed by another box? How do you prevent multiple boxes modifying similar data at the same time? How do you manage individual settings on a box by box basis? How do you handle video or music files stored on a central server? Do all the systems need to map their network drives the exact same way? Is it ok to place this requirement on the user? Will a server stream the content? These are the hard questions that have to be answered, regardless of how you implement a multi-seat system. Having all the boxes connect directly to a central database doesn't get rid of [i]any[/i] of these problems. I am not saying a client/server setup would immediately solve these problems either, but I [i]am[/i] saying that it would reduce the system requirements and complexity from the users point of view. So what advantages does using a enterprise level database solution bring us? Concurrent access can be done other ways so that is out. Sure SQL Server or MySQL is going to outperform SQLite, but the database is not the performance bottleneck for MediaPortal... [/QUOTE]

Verification