Reply to thread

Message

Yes, the main reason is that TVE3 is in code freeze since long time and the changes would be not compatible with the upcoming TVE3.5 (because it does use EntityFramework where SQLite is already supported).

Our primary motivation for the changes was to bring the matured and stable TVE3 as plugin into MP2, where SQLite is the default engine. But on the other hand there was no focus on support of MP1. I.e. the TvPlugin there does a direct access to the database, which is a bad design and would lead to issues with multi-seat systems: the client would need to access local sqlite db of the server, which could be solved by UNC network shares. But sqlite over network had some issues with possible data corruptions before, so for MP1 I'd not recomment it for multi-seat setups.

MP2 in contrast only uses UPnP for communication and no direct DB access, so this issue doesn't exists here.

<blockquote data-quote="morpheus_xx" data-source="post: 1180648" data-attributes="member: 48495">Yes, the main reason is that TVE3 is in code freeze since long time and the changes would be not compatible with the upcoming TVE3.5 (because it does use EntityFramework where SQLite is already supported).Our primary motivation for the changes was to bring the matured and stable TVE3 as plugin into MP2, where SQLite is the default engine. But on the other hand there was no focus on support of MP1. I.e. the TvPlugin there does a direct access to the database, which is a bad design and would lead to issues with multi-seat systems: the client would need to access local sqlite db of the server, which could be solved by UNC network shares. But sqlite over network had some issues with possible data corruptions before, so for MP1 I'd not recomment it for multi-seat setups.MP2 in contrast only uses UPnP for communication and no direct DB access, so this issue doesn't exists here.</blockquote>

[QUOTE="morpheus_xx, post: 1180648, member: 48495"] Yes, the main reason is that TVE3 is in code freeze since long time and the changes would be not compatible with the upcoming TVE3.5 (because it does use EntityFramework where SQLite is already supported). Our primary motivation for the changes was to bring the matured and stable TVE3 as plugin into MP2, where SQLite is the default engine. But on the other hand there was no focus on support of MP1. I.e. the TvPlugin there does a direct access to the database, which is a bad design and would lead to issues with multi-seat systems: the client would need to access local sqlite db of the server, which could be solved by UNC network shares. But sqlite over network had some issues with possible data corruptions before, so for MP1 I'd not recomment it for multi-seat setups. MP2 in contrast only uses UPnP for communication and no direct DB access, so this issue doesn't exists here. [/QUOTE]