I see 3.27 was released yesterday (and quickly followed up with 3.27.1.) I only discovered this because the post asking about VACUUM INTO gave me a clue that this might be a newly-released feature, so I went to the release-history page. We’ve been awaiting this release because it fixes a bad query bug we reported.
Was there an email posted to this list announcing the release? I didn’t see one, but it’s possible my spam filter went haywire.
As mentioned the release announcements is a separate mailing list, so people can get those without being deluged by stuff from this list. Pasting the announcement here.
From: sqlite-announce [mailto:[hidden email]] On Behalf Of Richard Hipp
Sent: Friday, February 08, 2019 10:20 AM
Subject: [sqlite-announce] Version 3.27.1
SQLite version 3.27.1 is now available on the SQLite website:
The only big enhancement in this release is the addition of the VACUUM
INTO command, which allows a database to be backed up atomically such
that the backup is minimal in size and contains no forensic traces of
deleted content. There are also enhancements to the command-line
interface and to some of the APIs such as sqlite3_deserialize(), and
general improvements to the robustness of SQLite when it is reading
and writing maliciously corrupted database files.
There was a 3.27.0 release yesterday. But a bug report came in just
after we had tagged the 3.27.0 release and before we had uploaded the
code and made the release announcement. The bug report was for a
query optimizer problem in 3.20.0 and was an older bug, completely
unrelated to recent changes. Rather than announce the 3.27.0 release,
then turn around an announce a 3.27.1 patch release the next day, we
just omitted the 3.27.0 release announcement, and thereby (hopefully)
spared people the trouble of having to upgrade twice. It would have
been better, of course, if the bug report had come to our attention
prior to tagging the 3.27.0 release so that we could have fixed the
problem in 3.27.0. But sometimes bug reports arrive at inopportune
Some of the Windows build products on the download page are still on
version 3.27.0. They will be updated to version 3.27.1 within 24
From: sqlite-users [mailto:[hidden email]] On Behalf Of Christian Schmitz
Sent: Friday, February 08, 2019 12:47 PM
To: SQLite mailing list
Subject: Re: [sqlite] Was there an announcement of 3.27?
> Am 08.02.2019 um 18:43 schrieb Jens Alfke <[hidden email]>:
> I see 3.27 was released yesterday (and quickly followed up with 3.27.1.) I
I'm sure someone savvier will correct me, but the source does indicate that 1 is "simple" and 2 "complex". It's not entirely clear, but it seems like " complex" is able to handle multiple diacritics on one base character and "simple" cannot?
sqlite-users mailing list
[hidden email] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
Thanks for reporting this. And the typos. I just added the following to
This option should be set to "0", "1" or "2". The default value is
"1". If it is set to "1" or "2", then diacritics are removed from Latin
script characters as described above. However, if it is set to "1", then
diacritics are not removed in the fairly uncommon case where a single
unicode codepoint is used to represent a character with more that one
diacritic. For example, diacritics are not removed from codepoint 0x1ED9
("LATIN SMALL LETTER O WITH CIRCUMFLEX AND DOT BELOW"). This is
technically a bug, but cannot be fixed without creating backwards
compatibility problems. If this option is set to "2", then diacritics
are correctly removed from all Latin characters.