On Mon, 2005-09-05 at 10:57 -0500, Ian Monroe wrote:
> I do not see how such a major change can be justified in a minor point
> release. For instance, currently amaroK does not work when using a
> sqlite database on Debian Sid since they package it with sqlite 3.2.5.
> Shouldn't this have waited for 4.0?

There are no plans at this time to ever release version 4.0.

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.

This is not a design change.  This is not an API change.
It does not break backwards compatibility.  All that changed
is that certain errors in the way SQLite is used are now
detected sooner rather than later.

D. Richard Hipp <[EMAIL PROTECTED]>

Reply via email to