>There are problems with some of them yet on SQLite, I've really only >tested them with 7.5.x and MySQL so I'm sure there are still a lot of >bugs if they are used with 7.6 and SQLite. I plan to test them a bit >more after 7.6 has been released, don't want to do it at the moment >because then I need to redo the testing when 7.6 is released since >there might be a lot changes between today and the release date. I've no doubt that there's not much to change to get it to function the same. However, any custom SQL that has been written by users (or generated from templates) could also be wrong. Users could just recreate them from the templates again, or power users would know what to change, but it's not something that can happen automatically during migration.
More of a concern would be performance related changes. eg. effects it may have on joins/indexes, which TrackStat will depend on. From my limited play with 7.6 (SQLite) Browsing music library seemed a lot slower. I'll try updating to latest though, because there was a recent bug fix for scan optimisation phase (wasn't being run). Also, a general concern of a change in DB engine is character traits. SBS has always had a multitude of issues with character encodings, unicode conversions, etc, and the DB engine could mean this will result in new issues/old issues reappearing. Maybe this could affect TrackStat. SQLite has some weird ideas. eg. a VARCHAR column has no length constraint, even if it defined with one. Maybe some of the weirdness that I remember from previous versions (quite a long time ago now) has been improved. _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
