>In my opinion, Logitech should really just say that only SQLite will be >supported in 7.6, it's pretty obvious that only SQLite is going to work >if they don't prioritize MySQL bugs. So in a scenario like this, why >even give users a choice ? > In my opinion, MySQL is much nicer, especially for development (better tools, can probe content whilst SBS is using the DB, better for optimising). It's much more likely to be suitable for larger libraries.
There really shouldn't be much involved for Logitech to provide both (after all, MySQL was working, SQLite should be additional), but agree that helpdesk support perhaps only support one. i.e. allow power users can continue to use MySQL, but by default use SQLite. >Not sure SQLite is faster, besides the scanner, 7.6 is faster than 7.5 >but that's also related to other changes, especially related to the >scanning process. > SBS shouldn't be heavy on DB access. I think performance problems are due to iffy SQL, or not DB issues (eg. file access, reading tags, etc). >I assume Logitech is resonably convinced that SQLite will work good >enough in the largest library they like to support, so this means that >the first point isn't an issue. > I don't see much evidence of comparitive testing. I think the main reason is due to Tiny SBS for Touch. SQLite was made for that environment, and thus reversed engineered into full SBS. If it wasn't for that, there would have been little reasons to switch database engine (again). To me, Tiny SBS = reduced functionality = use SQLite. Full SBS = MySQL. >To me this means that there is really >no reason for them to support MySQL at all, it just takes up valuable >development time that could be used to correct other bugs. To me, the development time has already been spent - MySQL integrated and working well/reliably in 7.5.x. SQLite is what has/is taking valuable development time, and not working well yet (with my experience of 7.6). There should be little to do with supporting MySQL, as it is already supported. When 7.6 is released, does that mean that helpdesk support will not answer support questions for 7.5.x and tell users they have to upgrade? >My suggestion the the community is just to accept SQLite, it's here to >stay and it's a lot better than it was a few years back. > If there were some comparitive results, showing usage with a big library, such as timing stats and memory usage, and 7.6 was working reliably enough to check that there were no other issues, such as character encoding issues, then it would be easier to accept. For me, MySQL is working well in 7.5, and there is no reason for me to need SQLite, which seems to be working less well. >Let's focus on the music related stuff which really matters instead of >technical issues like this which don't have any impact on our music >listening experience. > I'd actually prefer if Logitech focusses on making a stable platform, providing an extensible framework. I really don't think we'll ever see drastic changes in music browsing capabilities, and never with the same level of features that come from third-party plugins. Providing better development support to make creation of plugins easier is more likely to provide better power user facilities. Changing database engine should be easy with this app. There's hardly any difference in SQL queries, just how the DB is created and generally accessed. _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
