On Fri, Jul 15, 2011 at 16:59, Peter Samuelson <peter_at_p12n.org> wrote:
> [Greg Stein]
>> We have already worked around the bug in 3.7.7. There is no need to
>> disable support for that version.
> I think what he means is, remove our workaround for 3.7.7. There
> should be almost no installations, and if there are any, they will
> get an immediate error message upon svn invocation.
> google:// svn "database schema has changed"
> Second hit is http://freebsd.1045724.n5.nabble.com/devel-subversion-svn-Couldn-t-perform-atomic-initialization-svn-database-schema-has-changed-td4541240.html
> in which, if you scroll down a bit, someone mentions
> which is a request to update FreeBSD to SQLite 220.127.116.11.
> So the tradeoff is the (probably very few) SQLite 3.7.7 installations
> out there and how hard it is to find the cause of the error you get,
> vs. the complexity of our workaround, which I agree looks kinda ugly.
We've written the code. It works. We rarely have to look at the sqlite
initialization, so there is near-zero maintenance headache there.
Why should we break even ONE person on purpose? Why should we tell
that person to go upgrade SQLite?
And note that the 18.104.22.168 release note says that most people don't need it.
Just freakin' leave the code there. That one person that gets hit by
the removal will be very pissed off at us, and will spend more time
upgrading SQLite (if they can), then we would save any possible time
by simplifying the code.
Received on 2011-07-15 23:12:58 CEST