On 17-Jun-09, at 3:08 PM, Phil Meyer wrote:
It was a tad unfortunate that some virus scanners produced false positives with MySQL data files, giving it a bad name. It's not a fault with SqueezeCenter or MySQL, but with the virus scanners, etc. False positives could happen to any program. It could happen with SQLite.
Not really false positives. The problem is that by default, the scanners would access the temp files used by mysql. Mysql didn't like it when it wanted to erase or add to those files and found that it was locked up by another process. Thus, the transaction would fail. No bad name, just a limitation of using that service for something that seems to need the db on demand, beyond what it can stand to wait for virus scanners to move along.
I'm using trunk, so I haven't run it myself yet, but I recall reading that the debugging was on by default. This makes scanner speed less than it could be.That's true. Most people seem to be saying that SQLite is slower than their MySQL setup, but that the scanning code is faster; the net gain seems to be that the overrall scanning process is a bit slower.
-kdf
_______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
