>I might be wrong but I believe the main difference is not in the SQL, >the main difference is related to in-process database or a database >that runs as separate process. > Yes, and that's where I think that MySQL was already supported and working well, so for 7.6 it should be a matter of adding additional support for SQLite. Once done, there shouldn't be much to go wrong/change over time, as either platform should use a generic "how does app talk to database" solution.
>Logitech has taken advantage of the in-process paradigm of SQLite to >get a more effective system and this makes it more complicated to also >support MySQL. > Whether it's more effective is still open to debate, I think. It shouldn't be more complicated - just a different implementation of a generic interface. >The big problem is the time it takes to do QA on two databases. This >effectively duplicates the testing time on some parts of the system. If >Logitech only do QA on one of the databases the other one isn't going to >work reliably. > Should be setting up automated tests, and/or using targetted regression tests. If the generic interface works for some tests, the engine used for the back-end shouldn't matter. _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
