On 9/5/05, Ian Monroe <[EMAIL PROTECTED]> wrote: > > > > > SQLite has *never* supported the ability of a handle to be used > > by more than one thread. By luck, such use would sometimes work on > > some operating systems. But it would fail on others. Such a > > situation is very dangerous since if a developer is working on > > a system where the misuse of SQLite just happened to work, they > > might not detect their design error and then ship non-working code > > to a customer where it would fail. A minor change in check-in [2517] > > detects the misuse of SQLite on all systems and prevents it from > > working even by chance. This allows the problem to be detected > > early and corrected before it reaches a customer. > > But it has already reached our users. amaroK has never had a reported > problem with this. In this case "early" is a year or so too late. > > What about an --incorrect-behavior configuration option? Or a warning > to stderr instead?
Perhaps the gentoo default emerge build script should have the sqlite version specified instead of just assuming the default version. This cures the problem immediately while the authors consider their code changes.
