e9dcc55b7e
77 Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
apb
|
f15c02ef49 |
Update for tzdata2015f:
* Fix numbering in a comment; * Update version numbers; * Adjust a regex to recognise "Changes affecting.*data" without the word "format". |
||
|
apb
|
fd53cdca36 |
Import tzdata2015f from ftp://ftp.iana.org/tz/releases/tzdata2015f.tar.gz
Summary of changes in tzdata2015f (2015-08-10 18:06:56 -0700):
* North Korea switches to +0830 on 2015-08-15.
* Uruguay no longer observes DST.
* Moldova starts and ends DST at 00:00 UTC, not at 01:00 UTC.
* The two characters '%z' in a zone format now stand for the UTC
offset, e.g., '-07' for seven hours behind UTC and '+0530' for
five hours and thirty minutes ahead.
* Comments for America/Halifax and America/Glace_Bay have been improved.
* Data entries have been simplified for Atlantic/Canary, Europe/Simferopol,
Europe/Sofia, and Europe/Tallinn.
* Changes affecting documentation.
|
||
|
apb
|
65b14fa6e8 |
Import tzdata2015e from http://www.iana.org/time-zones/repository/releases/tzdata2015e.tar.gz
Summary of changes in tzdata2015e (2015-06-13 10:56:02 -0700):
* Morocco will suspend DST from 2015-06-14 03:00 through 2015-07-19 02:00,
not 06-13 and 07-18 as we had guessed.
* Assume Cayman Islands will observe DST starting next year, using US rules.
* The file 'iso3166.tab' now uses UTF-8, so that its entries can better
spell the names of Åland Islands, Côte d'Ivoire, and Réunion.
Summary of changes in tzdata2015d (2015-04-24 08:09:46 -0700):
* Egypt will not observe DST in 2015 and will consider canceling it
permanently. For now, assume no DST indefinitely.
* America/Whitehorse switched from UTC-9 to UTC-8 on 1967-05-28, not
1966-07-01.
* The abbreviations for Hawaii-Aleutian standard and daylight times
have been changed from HAST/HADT to HST/HDT, as per US Government
Printing Office style.
Summary of changes in tzdata2015c (2015-04-11 08:55:55 -0700):
* Egypt's spring-forward transition is at 24:00 on April's last Thursday,
not 00:00 on April's last Friday. This affects 2015, 2026, 2037,
2043, etc.
* Changes to pre-1991 Chile-related time stamps in America/Santiago,
Antarctica/Palmer, and Pacific/Easter.
* The America/Montreal zone has been turned into a link, as it differed
from an existing zone only for pre-1970 time stamps.
|
||
|
christos
|
f29f1289ff |
CID 1268629: Don't deref NULL (can't happen unless count is incorrect;
code safety). |
||
|
christos
|
0bb625c711 | help sun2 | ||
|
joerg
|
68f88a148d |
Drop condition around SIZEOF_SIZE_T to reduce diff against clean
version. The macro is only used on platforms without SIZE_MAX. |
||
|
joerg
|
d88be72d81 | Use unaligned access if the platform supports it. | ||
|
matt
|
0d7e891263 | Only include <immintrin.h> on x86 (32 or 64 bit). | ||
|
christos
|
05f8cb4da6 | there is no more lzma/lzma.h; it has been renamed to lzma/lzma12.h | ||
|
christos
|
cb571371b8 | adjust for 5.2.1 | ||
|
christos
|
880b10faa8 |
Date: 2015-02-26 16:53:44 +0200
Bump version and soname for 5.2.1.
Date: 2015-02-26 13:01:09 +0200
Update NEWS for 5.2.1.
Date: 2015-02-22 19:38:48 +0200
xz: Use pipe2() if available.
Date: 2015-02-21 23:40:26 +0200
liblzma: Fix a compression-ratio regression in LZMA1/2 in fast mode.
The bug was added in the commit
f48fce093b07aeda95c18850f5e086d9f2383380 and thus
affected 5.1.4beta and 5.2.0. Luckily the bug cannot
cause data corruption or other nasty things.
Date: 2015-02-21 23:00:19 +0200
xz: Fix the fcntl() usage when creating a pipe for the self-pipe trick.
Now it reads the old flags instead of blindly setting O_NONBLOCK.
The old code may have worked correctly, but this is better.
Date: 2015-02-10 15:29:34 +0200
Update THANKS.
Date: 2015-02-10 15:28:30 +0200
tuklib_cpucores: Use cpuset_getaffinity() on FreeBSD if available.
In FreeBSD, cpuset_getaffinity() is the preferred way to get
the number of available cores.
Thanks to Rui Paulo for the patch. I edited it slightly, but
hopefully I didn't break anything.
Date: 2015-02-09 22:08:37 +0200
xzdiff: Make the mktemp usage compatible with FreeBSD's mktemp.
Thanks to Rui Paulo for the fix.
Date: 2015-02-03 21:45:53 +0200
Add a few casts to tuklib_integer.h to silence possible warnings.
I heard that Visual Studio 2013 gave warnings without the casts.
Thanks to Gabi Davar.
Date: 2015-01-26 21:24:39 +0200
liblzma: Set LZMA_MEMCMPLEN_EXTRA depending on the compare method.
Date: 2015-01-26 20:40:16 +0200
Update THANKS.
Date: 2015-01-26 20:39:28 +0200
liblzma: Silence harmless Valgrind errors.
Thanks to Torsten Rupp for reporting this. I had
forgotten to run Valgrind before the 5.2.0 release.
Date: 2015-01-09 21:50:19 +0200
xz: Fix comments.
Date: 2015-01-09 21:35:06 +0200
Update THANKS.
Date: 2015-01-09 21:34:06 +0200
xz: Don't fail if stdout doesn't support O_NONBLOCK.
This is similar to the case with stdin.
Thanks to Brad Smith for the bug report and testing
on OpenBSD.
Date: 2015-01-07 19:18:20 +0200
xz: Fix a memory leak in DOS-specific code.
Date: 2015-01-07 19:08:06 +0200
xz: Don't fail if stdin doesn't support O_NONBLOCK.
It's a problem at least on OpenBSD which doesn't support
O_NONBLOCK on e.g. /dev/null. I'm not surprised if it's
a problem on other OSes too since this behavior is allowed
in POSIX-1.2008.
The code relying on this behavior was committed in June 2013
and included in 5.1.3alpha released on 2013-10-26. Clearly
the development releases only get limited testing.
Date: 2015-01-06 20:30:15 +0200
Tests: Don't hide unexpected error messages in test_files.sh.
Hiding them makes no sense since normally there's no error
when testing the "good" files. With "bad" files errors are
expected and then it makes sense to keep the messages hidden.
Date: 2014-12-30 11:17:16 +0200
Update Solaris notes in INSTALL.
Mention the possible "make check" failure on Solaris in the
Solaris-specific section of INSTALL. It was already in
section 4.5 but it is better mention it in the OS-specific
section too.
Date: 2014-12-26 12:00:05 +0200
Build: POSIX shell isn't required if scripts are disabled.
Date: 2014-12-21 20:48:37 +0200
DOS: Update Makefile.
Date: 2014-12-21 19:50:38 +0200
Windows: Fix bin_i486 to bin_i686 in build.bash.
Date: 2014-12-21 18:58:44 +0200
Docs: Use lzma_cputhreads() in 04_compress_easy_mt.c.
Date: 2014-12-21 18:56:44 +0200
Docs: Update docs/examples/00_README.txt.
Date: 2014-12-21 18:11:17 +0200
Bump version and soname for 5.2.0.
I know that soname != app version, but I skip AGE=1
in -version-info to make the soname match the liblzma
version anyway. It doesn't hurt anything as long as
it doesn't conflict with library versioning rules.
Date: 2014-12-21 18:05:03 +0200
Avoid variable-length arrays in the debug programs.
Date: 2014-12-21 18:01:45 +0200
Build: Include 04_compress_easy_mt.c in the tarball.
Date: 2014-12-21 18:00:38 +0200
Fix build when --disable-threads is used.
Date: 2014-12-21 15:56:15 +0100
po/fr: improve wording for help for --lzma1/--lzma2.
Date: 2014-12-21 15:55:48 +0100
po/fr: missing line in translation of --extreme.
Date: 2014-12-21 14:32:33 +0200
Update NEWS for 5.2.0.
Date: 2014-12-21 14:32:22 +0200
Update NEWS for 5.0.8.
Date: 2014-12-21 14:07:54 +0200
xz: Fix a comment.
Date: 2014-12-20 20:43:14 +0200
Update INSTALL about the dependencies of the scripts.
Date: 2014-12-20 20:42:33 +0200
Windows: Update build instructions.
Date: 2014-12-20 20:41:48 +0200
Windows: Update the build script and README-Windows.txt.
The 32-bit build is now for i686 or newer because the
prebuilt MinGW-w64 toolchains include i686 code in the
executables even if one uses -march=i486.
The build script builds 32-bit SSE2 enabled version too.
Run-time detection of SSE2 support would be nice (on any OS)
but it's not implemented in XZ Utils yet.
Date: 2014-12-19 15:51:50 +0200
Windows: Define TUKLIB_SYMBOL_PREFIX in config.h.
It is to keep all symbols in the lzma_ namespace.
Date: 2014-12-16 21:00:09 +0200
xz: Update the man page about --threads.
Date: 2014-12-16 20:57:43 +0200
xz: Update the man page about --block-size.
Date: 2014-12-10 22:26:57 +0100
po/fr: several more translation updates: reword and handle --ignore-check.
Date: 2014-12-10 22:23:01 +0100
po/fr: yet another place where my email address had to be updated.
Date: 2014-12-10 22:22:20 +0100
po/fr: fix several typos that have been around since the beginning.
Date: 2014-12-03 20:02:31 +0100
po/fr: last batch of new translations for now.
Four new error messages.
Date: 2014-12-03 20:01:32 +0100
po/fr: translations for --threads, --block-size and --block-list.
Date: 2014-12-03 20:00:53 +0100
po/fr: remove fuzzy marker for error messages that will be kept in English.
The following is a copy of a comment inside fr.po:
Note from translator on "file status flags".
The following entry is kept un-translated on purpose. It is difficult to
translate and should only happen in exceptional circumstances which means
that translating would:
- lose some of the meaning
- make it more difficult to look up in search engines; it might happen one
in
a million times, if we dilute the error message in 20 languages, it will be
almost impossible to find an explanation and support for the error.
Date: 2014-12-03 19:58:25 +0100
po/fr: several minor updates and better wording.
Meaning doesn't change at all: it's only for better wording and/or
formatting of a few strings.
Date: 2014-12-03 19:56:12 +0100
po/fr: update my email address and copyright years.
Date: 2014-11-26 10:08:26 +0100
fr.po: commit file after only "update-po" so actual is readable.
Date: 2014-12-02 20:04:07 +0200
liblzma: Document how lzma_mt.block_size affects memory usage.
Date: 2014-11-28 20:07:18 +0200
Update INSTALL about a "make check" failure in test_scripts.sh.
Date: 2014-11-26 20:12:27 +0200
Remove LZMA_UNSTABLE macro.
Date: 2014-11-26 20:10:33 +0200
liblzma: Update lzma_stream_encoder_mt() API docs.
Date: 2014-11-25 12:32:05 +0200
liblzma: Verify the filter chain in threaded encoder initialization.
This way an invalid filter chain is detected at the Stream
encoder initialization instead of delaying it to the first
call to lzma_code() which triggers the initialization of
the actual filter encoder(s).
Date: 2014-11-17 19:11:49 +0200
Build: Update m4/ax_pthread.m4 from Autoconf Archive.
Date: 2014-11-17 18:52:21 +0200
Build: Replace obsolete AC_HELP_STRING with AS_HELP_STRING.
Date: 2014-11-17 18:43:19 +0200
Build: Fix Autoconf warnings about escaped backquotes.
Thanks to Daniel Richard G. for pointing out that it's
good to sometimes run autoreconf -fi with -Wall.
Date: 2014-11-10 18:54:40 +0200
xzdiff: Use mkdir if mktemp isn't available.
Date: 2014-11-10 18:45:01 +0200
xzdiff: Create a temporary directory to hold a temporary file.
This avoids the possibility of "File name too long" when
creating a temp file when the input file name is very long.
This also means that other users on the system can no longer
see the input file names in /tmp (or whatever $TMPDIR is)
since the temporary directory will have a generic name. This
usually doesn't matter since on many systems one can see
the arguments given to all processes anyway.
The number X chars to mktemp where increased from 6 to 10.
Note that with some shells temp files or dirs won't be used at all.
Date: 2014-11-10 15:38:47 +0200
liblzma: Fix lzma_mt.preset in lzma_stream_encoder_mt_memusage().
It read the filter chain from a wrong variable. This is a similar
bug that was fixed in 9494fb6d0ff41c585326f00aa8f7fe58f8106a5e.
Date: 2014-11-10 14:49:55 +0200
Update THANKS.
Date: 2014-10-29 21:28:25 +0200
Update .gitignore files.
Date: 2014-10-29 21:15:35 +0200
Build: Prepare to support Automake's subdir-objects.
Due to a bug in Automake, subdir-objects won't be enabled
for now.
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=17354
Thanks to Daniel Richard G. for the original patches.
Date: 2014-10-24 20:09:29 +0300
Translations: Update the Italian translation.
Thanks to Milo Casagrande.
Date: 2014-10-18 18:51:45 +0300
Translations: Update the Polish translation.
Thanks to Jakub Bogusz.
Date: 2014-10-14 17:30:30 +0200
l10n: de.po: Change translator email address.
Although the old address is still working, the new one should
be preferred. So this commit changes all three places in de.po
accordingly.
Signed-off-by: Andre Noll <maan@tuebingen.mpg.de>
Date: 2014-10-14 17:30:29 +0200
l10n: de.po: Update German translation
Signed-off-by: Andre Noll <maan@systemlinux.org>
Date: 2014-10-14 17:30:28 +0200
l10n: de.po: Fix typo: Schießen -> Schließen.
That's a funny one since "schießen" means to shoot :)
Signed-off-by: Andre Noll <maan@systemlinux.org>
Date: 2014-10-09 19:42:26 +0300
Update THANKS.
Date: 2014-10-09 19:41:51 +0300
Add support for AmigaOS/AROS to tuklib_physmem().
Thanks to Fredrik Wikstrom.
Date: 2014-10-09 18:42:14 +0300
xzgrep: Avoid passing both -q and -l to grep.
The behavior of grep -ql varies:
- GNU grep behaves like grep -q.
- OpenBSD grep behaves like grep -l.
POSIX doesn't make it 100 % clear what behavior is expected.
Anyway, using both -q and -l at the same time makes no sense
so both options simply should never be used at the same time.
Thanks to Christian Weisgerber.
Date: 2014-09-25 09:22:45 +0700
l10n: vi.po: Update Vietnamese translation
Signed-off-by: Trần Ngọc Quân <vnwildman@gmail.com>
Date: 2014-09-25 18:38:48 +0300
Build: Detect supported compiler warning flags better.
Clang and nowadays also GCC accept any -Wfoobar option
but then may give a warning that an unknown warning option
was specified. To avoid adding unsupported warning options,
the options are now tested with -Werror.
Thanks to Charles Diza.
Date: 2014-09-20 21:01:21 +0300
Update NEWS for 5.0.7.
Date: 2014-09-20 19:42:56 +0300
liblzma: Fix a portability problem in Makefile.am.
POSIX supports $< only in inference rules (suffix rules).
Using it elsewhere is a GNU make extension and doesn't
work e.g. with OpenBSD make.
Thanks to Christian Weisgerber for the patch.
Date: 2014-09-14 21:54:09 +0300
Bump the version number to 5.1.4beta.
Date: 2014-09-14 21:50:13 +0300
Update NEWS for 5.0.6 and 5.1.4beta.
Date: 2014-09-14 21:02:41 +0300
Update TODO.
Date: 2014-08-05 22:32:36 +0300
xz: Add --ignore-check.
Date: 2014-08-05 22:15:07 +0300
liblzma: Add support for LZMA_IGNORE_CHECK.
Date: 2014-08-05 22:03:30 +0300
liblzma: Add support for lzma_block.ignore_check.
Note that this slightly changes how lzma_block_header_decode()
has been documented. Earlier it said that the .version is set
to the lowest required value, but now it says that the .version
field is kept unchanged if possible. In practice this doesn't
affect any old code, because before this commit the only
possible .version was 0.
Date: 2014-08-04 19:25:58 +0300
liblzma: Use lzma_memcmplen() in the BT3 match finder.
I had missed this when writing the commit
5db75054e900fa06ef5ade5f2c21dffdd5d16141.
Thanks to Jun I Jin.
Date: 2014-08-04 00:25:44 +0300
Update THANKS.
Date: 2014-08-03 21:32:25 +0300
liblzma: SHA-256: Optimize the Maj macro slightly.
The Maj macro is used where multiple things are added
together, so making Maj a sum of two expressions allows
some extra freedom for the compiler to schedule the
instructions.
I learned this trick from
<http://www.hackersdelight.org/corres.txt>.
Date: 2014-08-03 21:08:12 +0300
liblzma: SHA-256: Optimize the way rotations are done.
This looks weird because the rotations become sequential,
but it helps quite a bit on both 32-bit and 64-bit x86:
- It requires fewer instructions on two-operand
instruction sets like x86.
- It requires one register less which matters especially
on 32-bit x86.
I hope this doesn't hurt other archs.
I didn't invent this idea myself, but I don't remember where
I saw it first.
Date: 2014-08-03 20:38:13 +0300
liblzma: SHA-256: Remove the GCC #pragma that became unneeded.
The unrolling in the previous commit should avoid the
situation where a compiler may think that an uninitialized
variable might be accessed.
Date: 2014-08-03 20:33:38 +0300
liblzma: SHA-256: Unroll a little more.
This way a branch isn't needed for each operation
to choose between blk0 and blk2, and still the code
doesn't grow as much as it would with full unrolling.
Date: 2014-08-03 19:56:43 +0300
liblzma: SHA-256: Do the byteswapping without a temporary buffer.
Date: 2014-07-25 22:38:28 +0300
liblzma: Use lzma_memcmplen() in normal mode of LZMA.
Two locations were not changed yet because the simplest change
assumes that the initial "len" may be greater than "limit".
Date: 2014-07-25 22:30:38 +0300
liblzma: Simplify LZMA fast mode code by using memcmp().
Date: 2014-07-25 22:29:49 +0300
liblzma: Use lzma_memcmplen() in fast mode of LZMA.
Date: 2014-07-25 21:16:23 +0300
Update THANKS.
Date: 2014-07-25 21:15:07 +0300
liblzma: Use lzma_memcmplen() in the match finders.
This doesn't change the match finder output.
Date: 2014-07-25 20:57:20 +0300
liblzma: Add lzma_memcmplen() for fast memory comparison.
This commit just adds the function. Its uses will be in
separate commits.
This hasn't been tested much yet and it's perhaps a bit early
to commit it but if there are bugs they should get found quite
quickly.
Thanks to Jun I Jin from Intel for help and for pointing out
that string comparison needs to be optimized in liblzma.
Date: 2014-07-12 21:10:09 +0300
Update THANKS.
Date: 2014-07-12 20:06:08 +0300
Translations: Add Vietnamese translation.
Thanks to Trần Ngọc Quân.
Date: 2014-06-29 20:54:14 +0300
xz: Update the help message of a few options.
Updated: --threads, --block-size, and --block-list
Added: --flush-timeout
Date: 2014-06-18 22:07:06 +0300
xz: Use lzma_cputhreads() instead of own copy of tuklib_cpucores().
Date: 2014-06-18 22:04:24 +0300
liblzma: Add lzma_cputhreads().
Date: 2014-06-18 19:11:52 +0300
xz: Check for filter chain compatibility for --flush-timeout.
This avoids LZMA_PROG_ERROR from lzma_code() with filter chains
that don't support LZMA_SYNC_FLUSH.
Date: 2014-06-13 19:21:54 +0300
xzgrep: List xzgrep_expected_output in tests/Makefile.am.
Date: 2014-06-13 18:58:22 +0300
xzgrep: Improve the test script.
Now it should be close to the functionality of the original
version by Pavel Raiskup.
Date: 2014-06-11 21:03:25 +0300
xzgrep: Add a test for the previous fix.
This is a simplified version of Pavel Raiskup's
original patch.
Date: 2014-06-11 20:43:28 +0300
xzgrep: exit 0 when at least one file matches.
Mimic the original grep behavior and return exit_success when
at least one xz compressed file matches given pattern.
Original bugreport:
https://bugzilla.redhat.com/show_bug.cgi?id=1108085
Thanks to Pavel Raiskup for the patch.
Date: 2014-06-09 21:21:24 +0300
xz: Force single-threaded mode when --flush-timeout is used.
Date: 2014-05-25 22:05:39 +0300
Update THANKS.
Date: 2014-05-25 21:45:56 +0300
liblzma: Use lzma_alloc_zero() in LZ encoder initialization.
This avoids a memzero() call for a newly-allocated memory,
which can be expensive when encoding small streams with
an over-sized dictionary.
To avoid using lzma_alloc_zero() for memory that doesn't
need to be zeroed, lzma_mf.son is now allocated separately,
which requires handling it separately in normalize() too.
Thanks to Vincenzo Innocente for reporting the problem.
Date: 2014-05-25 19:25:57 +0300
liblzma: Add the internal function lzma_alloc_zero().
Date: 2014-05-08 18:03:09 +0300
xz: Fix uint64_t vs. size_t which broke 32-bit build.
Thanks to Christian Hesse.
Date: 2014-05-04 11:09:11 +0300
Docs: Update comments to refer to lzma/lzma12.h in example programs.
Date: 2014-05-04 11:07:17 +0300
liblzma: Rename the private API header lzma/lzma.h to lzma/lzma12.h.
It can be confusing that two header files have the same name.
The public API file is still lzma.h.
Date: 2014-04-25 17:53:42 +0300
Build: Fix the combination of --disable-xzdec --enable-lzmadec.
In this case "make install" could fail if the man page directory
didn't already exist at the destination. If it did exist, a
dangling symlink was created there. Now the link is omitted
instead. This isn't the best fix but it's better than the old
behavior.
Date: 2014-04-25 17:44:26 +0300
Build: Add --disable-doc to configure.
Date: 2014-04-24 18:06:24 +0300
Update INSTALL.
Add a note about failing "make check". The source of
the problem should be fixed in libtool (if it really is
a libtool bug and not mine) but I'm unable to spend time
on that for now. Thanks to Nelson H. F. Beebe for reporting
the issue.
Add a note about a possible need to run "ldconfig" after
"make install".
Date: 2014-04-09 17:26:10 +0300
xz: Rename a variable to avoid a namespace collision on Solaris.
I don't know the details but I have an impression that there's
no problem in practice if using GCC since people have built xz
with GCC (without patching xz), but renaming the variable cannot
hurt either.
Thanks to Mark Ashley.
Date: 2014-01-29 20:19:41 +0200
Docs: Add example program for threaded encoding.
I didn't add -DLZMA_UNSTABLE to Makefile so one has to
specify it manually as long as LZMA_UNSTABLE is needed.
Date: 2014-01-29 20:13:51 +0200
liblzma: Fix lzma_mt.preset not working with lzma_stream_encoder_mt().
It read the filter chain from a wrong variable.
Date: 2014-01-20 11:20:40 +0200
liblzma: Fix typo in a comment.
Date: 2014-01-12 19:38:43 +0200
Windows: Add config.h for building liblzma with MSVC 2013.
This is for building liblzma. Building xz tool too requires
a little more work. Maybe it will be supported, but for most
MSVC users it's enough to be able to build liblzma.
C99 support in MSVC 2013 is almost usable which is a big
improvement over earlier versions. It's "almost" because
there's a dumb bug that breaks mixed declarations after
an "if" statements unless the "if" statement uses braces:
https://connect.microsoft.com/VisualStudio/feedback/details/808650/visual-studio-2013-c99-compiler-bug
https://connect.microsoft.com/VisualStudio/feedback/details/808472/c99-support-of-mixed-declarations-and-statements-fails-with-certain-types-and-constructs
Hopefully it will get fixed. Then liblzma should be
compilable with MSVC 2013 without patching.
Date: 2014-01-12 17:41:14 +0200
xz: Fix a comment.
Date: 2014-01-12 17:04:33 +0200
Windows: Add MSVC defines for inline and restrict keywords.
Date: 2014-01-12 16:44:52 +0200
liblzma: Avoid C99 compound literal arrays.
MSVC 2013 doesn't like them. Maybe they aren't so good
for readability either since many aren't used to them.
Date: 2014-01-12 12:50:30 +0200
liblzma: Remove a useless C99ism from sha256.c.
Unsurprisingly it makes no difference in compiled output.
Date: 2014-01-12 12:17:08 +0200
xz: Fix use of wrong variable.
Since the only call to suffix_set() uses optarg
as the argument, fixing this bug doesn't change
the behavior of the program.
Date: 2014-01-12 12:11:36 +0200
Fix typos in comments.
Date: 2013-11-26 18:20:16 +0200
Update THANKS.
Date: 2013-11-26 18:20:09 +0200
liblzma: Document the need for block->check for lzma_block_header_decode().
Thanks to Tomer Chachamu.
Date: 2013-11-12 16:38:57 +0200
xz: Update the man page about --block-size and --block-list.
Date: 2013-11-12 16:30:53 +0200
Update THANKS.
Date: 2013-11-12 16:29:48 +0200
xz: Make --block-list and --block-size work together in single-threaded.
Previously, --block-list and --block-size only worked together
in threaded mode. Boundaries are specified by --block-list, but
--block-size specifies the maximum size for a Block. Now this
works in single-threaded mode too.
Thanks to James M Leddy for the original patch.
Date: 2013-10-26 13:26:14 +0300
Bump the version number to 5.1.3alpha.
Date: 2013-10-26 13:25:02 +0300
Update NEWS for 5.1.3alpha.
Date: 2013-10-26 12:47:04 +0300
Update TODO.
Date: 2013-10-25 22:41:28 +0300
xz: Document behavior of --block-list with threads.
This needs to be updated before 5.2.0.
Date: 2013-10-22 20:03:12 +0300
xz: Document --flush-timeout=TIMEOUT on the man page.
Date: 2013-10-22 19:51:55 +0300
xz: Take advantage of LZMA_FULL_BARRIER with --block-list.
Now if --block-list is used in threaded mode, the encoder
won't need to flush at each Block boundary specified via
--block-list. This improves performance a lot, making
threading helpful with --block-list.
The flush timer was reset after LZMA_FULL_FLUSH but since
LZMA_FULL_BARRIER doesn't flush, resetting the timer is
no longer done.
Date: 2013-10-02 20:05:23 +0300
liblzma: Support LZMA_FULL_FLUSH and _BARRIER in threaded encoder.
Now --block-list=SIZES works with in the threaded mode too,
although the performance is still bad due to the use of
LZMA_FULL_FLUSH instead of the new LZMA_FULL_BARRIER.
Date: 2013-10-02 12:55:11 +0300
liblzma: Add LZMA_FULL_BARRIER support to single-threaded encoder.
In the single-threaded encoder LZMA_FULL_BARRIER is simply
an alias for LZMA_FULL_FLUSH.
Date: 2013-09-17 11:57:51 +0300
liblzma: Add block_buffer_encoder.h into Makefile.inc.
This should have been in b465da5988dd59ad98fda10c2e4ea13d0b9c73bc.
Date: 2013-09-17 11:55:38 +0300
xz: Add a missing test for TUKLIB_DOSLIKE.
Date: 2013-09-17 11:52:28 +0300
Add native threading support on Windows.
Now liblzma only uses "mythread" functions and types
which are defined in mythread.h matching the desired
threading method.
Before Windows Vista, there is no direct equivalent to
pthread condition variables. Since this package doesn't
use pthread_cond_broadcast(), pre-Vista threading can
still be kept quite simple. The pre-Vista code doesn't
use anything that wasn't already available in Windows 95,
so the binaries should run even on Windows 95 if someone
happens to care.
Date: 2013-09-11 14:40:35 +0300
Build: Remove a comment about Automake 1.10 from configure.ac.
The previous commit supports silent rules and that requires
Automake 1.11.
Date: 2013-09-09 20:37:03 +0300
Build: Create liblzma.pc in a src/liblzma/Makefile.am.
Previously it was done in configure, but doing that goes
against the Autoconf manual. Autoconf requires that it is
possible to override e.g. prefix after running configure
and that doesn't work correctly if liblzma.pc is created
by configure.
A potential downside of this change is that now e.g.
libdir in liblzma.pc is a standalone string instead of
being defined via ${prefix}, so if one overrides prefix
when running pkg-config the libdir won't get the new value.
I don't know if this matters in practice.
Thanks to Vincent Torri.
Date: 2013-08-04 15:24:09 +0300
Fix the previous commit which broke the build.
Apparently I didn't even compile-test the previous commit.
Thanks to Christian Hesse.
Date: 2013-08-03 13:52:58 +0300
Windows: Add Windows support to tuklib_cpucores().
It is used for Cygwin too. I'm not sure if that is
a good or bad idea.
Thanks to Vincent Torri.
Date: 2013-08-02 15:59:46 +0200
macosx: separate liblzma package
Date: 2013-08-02 15:58:44 +0200
macosx: set minimum to leopard
Date: 2011-08-07 13:13:30 +0200
move configurables into variables
Date: 2013-07-15 14:08:41 +0300
Update THANKS.
Date: 2013-07-15 14:08:02 +0300
Build: Fix the detection of missing CRC32.
Thanks to Vincent Torri.
Date: 2013-07-04 14:18:46 +0300
xz: Add preliminary support for --flush-timeout=TIMEOUT.
When --flush-timeout=TIMEOUT is used, xz will use
LZMA_SYNC_FLUSH if read() would block and at least
TIMEOUT milliseconds has elapsed since the previous flush.
This can be useful in realtime-like use cases where the
data is simultanously decompressed by another process
(possibly on a different computer). If new uncompressed
input data is produced slowly, without this option xz could
buffer the data for a long time until it would become
decompressible from the output.
If TIMEOUT is 0, the feature is disabled. This is the default.
This commit affects the compression side. Using xz for
the decompression side for the above purpose doesn't work
yet so well because there is quite a bit of input and
output buffering when decompressing.
The --long-help or man page were not updated yet.
The details of this feature may change.
Date: 2013-07-04 13:41:03 +0300
xz: Don't set src_eof=true after an I/O error because it's useless.
Date: 2013-07-04 13:25:11 +0300
xz: Fix the test when to read more input.
Testing for end of file was no longer correct after full flushing
became possible with --block-size=SIZE and --block-list=SIZES.
There was no bug in practice though because xz just made a few
unneeded zero-byte reads.
Date: 2013-07-04 12:51:57 +0300
xz: Move some of the timing code into mytime.[hc].
This switches units from microseconds to milliseconds.
New clock_gettime(CLOCK_MONOTONIC) will be used if available.
There is still a fallback to gettimeofday().
Date: 2013-07-01 14:35:03 +0300
Update THANKS.
Date: 2013-07-01 14:34:11 +0300
xz: Silence a warning seen with _FORTIFY_SOURCE=2.
Thanks to Christian Hesse.
|
||
|
apb
|
b3f66a3d8a | Actually create the "done" files, and test them for existence. | ||
|
apb
|
0ba7d01cae |
Update tzdata2netbsd for tzdata2015b.
* Edit version numbers. * Make the script deal better with being re-run multiple times. It now keeps a status file for each non-trivial step, and doesn't repeat the step if the sttaus file exists. * Instead of spawning a subshell to resolve merge conflicts, print a message and exit, with a suggestion to rte-run the script after conflicts are resolved. * Check whether there are any conflicts before trying to do anything about conflicts. |
||
|
apb
|
555a785a32 |
Import tzdata2015b from ftp://ftp.iana.org/tz/releases/tzdata2015b.tar.gz
Summary of changes in tzdata2015b (2015-03-19 23:28:11 -0700):
* Mongolia will start observing DST again in 2015, from the last
Saturday in March at 02:00 to the last Saturday in September at 00:00.
* Palestine will start DST on March 28, not March 27, in 2015.
* The 1982 zone shift in Pacific/Easter has been corrected, fixing a 2015a
regression.
* Some more zones have been turned into links, when they differed
from existing zones only for older time stamps.
* Correct the 1992-2010 DST abbreviation in Volgograd from "MSK" to "MSD".
* Changes affecting commentary.
|
||
|
apb
|
12a1cf4f57 |
Import tzdata2015a from ftp://ftp.iana.org/tz/releases/tzdata2015a.tar.gz
Summary of changes in tzdata2015a (2015-01-29 22:35:20 -0800):
* The Mexican state of Quintana Roo, represented by America/Cancun,
will shift from Central Time with DST to Eastern Time without DST
on 2015-02-01 at 02:00.
* Chile will not change clocks in April or thereafter; its new standard time
will be its old daylight saving time. This affects America/Santiago,
Pacific/Easter, and Antarctica/Palmer. (Thanks to Juan Correa.)
* New leap second 2015-06-30 23:59:60 UTC as per IERS Bulletin C 49.
* Iceland observed DST in 1919 and 1921, and its 1939 fallback
transition was Oct.
* Some more zones have been turned into links, when they differed
from existing zones only for older time stamps.
* Changes affecting commentary.
|
||
|
apb
|
1f80bef788 |
Import tzdata2014j from ftp://ftp.iana.org/tz/releases/tzdata2014j.tar.gz
Summary of changes in tzdata2014j (2014-11-10 17:37:11 -0800):
* Turks & Caicos' switch from US eastern time to UTC-4 year-round
did not occur on 2014-11-02 at 02:00.
* Many pre-1989 time stamps have been corrected for Asia/Seoul and
Asia/Pyongyang, based on sources for the Korean-language Wikipedia
entry for time in Korea.
* Some more zones have been turned into links, when they differed
from existing zones only for older (pre-1970) time stamps.
* Changes affecting commentary.
Summary of changes in tzdata2014i (2014-10-21 22:04:57 -0700):
* Pacific/Fiji will observe DST from 2014-11-02 02:00 to 2015-01-18 03:00.
* A new Zone Pacific/Bougainville, for the part of Papua New Guinea
that plans to switch from UTC+10 to UTC+11 on 2014-12-28 at 02:00.
* Since Belarus is not changing its clocks even though Moscow is,
the time zone abbreviation in Europe/Minsk is changing from FET
to its more-traditional value MSK on 2014-10-26 at 01:00.
* The new abbreviation IDT stands for the pre-1976 use of UT+8 in
Indochina, to distinguish it better from ICT (UT+7).
* Many time stamps have been corrected for Asia/Ho_Chi_Minh before 1976.
Asia/Ho_Chi_Minh has been added to zone1970.tab, to give tzselect
users in Vietnam two choices, since north and south Vietnam
disagreed after our 1970 cutoff.
* Asia/Phnom_Penh and Asia/Vientiane have been turned into links, as
they differed from existing zones only for older (pre-1970) time stamps.
* Changes affecting commentary.
|
||
|
apb
|
2eedb5803b |
Update tzdata2netbsd for 2014i.
The NEWS file has been included in the tzdata tarball since 2014g, so don't mention the separate NEWS URL in the prototype CVS log message. |
||
|
apb
|
94442e1f49 |
Import tzdata2014i from ftp://ftp.iana.org/tz/releases/tzdata2014i.tar.gz
Summary of changes in tzdata2014i (2014-10-21 22:04:57 -0700):
* Pacific/Fiji will observe DST from 2014-11-02 02:00 to 2015-01-18 03:00.
Guess that future years will use a similar pattern.
* A new Zone Pacific/Bougainville, for the part of Papua New Guinea
that plans to switch from UTC+10 to UTC+11 on 2014-12-28 at 02:00.
* Since Belarus is not changing its clocks even though Moscow is,
the time zone abbreviation in Europe/Minsk is changing from FET
to its more-traditional value MSK on 2014-10-26 at 01:00.
* The new abbreviation IDT stands for the pre-1976 use of UT+8 in
Indochina, to distinguish it better from ICT (UT+7).
* Many time stamps have been corrected for Asia/Ho_Chi_Minh before 1976.
Asia/Ho_Chi_Minh has been added to zone1970.tab, since
north and south Vietnam disagreed after our 1970 cutoff.
* Asia/Phnom_Penh and Asia/Vientiane have been turned into links, as
they differed from existing zones only for pre-1970 time stamps.
* Changes affecting commentary.
|
||
|
apb
|
10fb7dcce0 |
Import tzdata2014h from ftp://ftp.iana.org/tz/releases/tzdata2014h.tar.gz
Summary of changes in tzdata2014h (2014-09-25 18:59:03 -0700):
* America/Jamaica's 1974 spring-forward transition was Jan. 6, not Apr. 28.
* Shanks says Asia/Novokuznetsk switched from LMT (not "NMT") on 1924-05-01,
not 1920-01-06.
* Some more zones have been turned into links, when they differed
from existing zones only for older time stamps. As usual,
these changes affect UTC offsets in pre-1970 time stamps only.
Their old contents have been moved to the 'backzone' file.
The affected zones are: Africa/Blantyre, Africa/Bujumbura,
Africa/Gaborone, Africa/Harare, Africa/Kigali, Africa/Lubumbashi,
Africa/Lusaka, Africa/Maseru, and Africa/Mbabane.
* Changes affecting documentation and commentary.
|
||
|
apb
|
e23e44ad12 |
Updated import script for tzdata2014g.
Aso added "cd" commands that were missed in the recent move from src/share/zoneinfo to external/public-domain/tz. |
||
|
apb
|
acd39795c2 |
Import tzdata2014g from ftp://ftp.iana.org/tz/releases/tzdata2014g.tar.gz
Summary of changes in tzdata2014g (2014-08-28 12:31:23 -0700):
* Turks & Caicos is switching from US eastern time to UTC-4 year-round,
modeled as a switch from EST/EDT to AST on 2014-11-02 at 02:00.
* Time in Russia or the USSR before 1926 or so has been corrected by
a few seconds for several zones, and a few minutes for
Asia/Yekaterinburg.
* The Portuguese decree of 1911-05-26 took effect on 1912-01-01, not
on the date of the decree. This affects 1911 time stamps in
Africa/Bissau, Africa/Luanda, Atlantic/Azores, and Atlantic/Madeira.
* Lisbon's pre-1912 GMT offset was -0:36:45 (rounded from -0:36:44.68),
not -0:36:32.
* Asia/Dhaka ended DST on 2009-12-31 at 24:00, not 23:59.
* A new file 'backzone' contains data which may appeal to
connoisseurs of old time stamps, although it is out of scope for
the tz database, is often poorly sourced, and contains some data
that is known to be incorrect.
* Some more zones have been turned into links, when they differed
from existing zones only for older time stamps. As usual,
these changes affect UTC offsets in pre-1970 time stamps only.
Their old contents have been moved to the 'backzone' file.
* Changes affecting documentation and commentary.
|
||
|
apb
|
580ccc375e |
Adapt tzdata2netbsd script to the new source location.
* Change src/share/zoneinfo to src/external/public-domain/tz. * The NEWS file is not distributed in the tzdata tar.gz file, but it logically belongs with it. We were already downloading the NEWS file from a different location, but now we also add it to the import directory. |
||
|
apb
|
2c9001de40 |
Hook external/public-domain/tz into the build, and unhook share/zoneinfo.
The timezone files are still installed in ${DESTDIR}/usr/share/zoneinfo/**,
and they are identical before and after this change.
This is almost the last step in moving NetBSD's tzdata sources from
share/zoneinfo to external/public/tz/dist, to ease future maintenance.
All that remains is to delete src/share/zoneinfo, but that will be
delayed for a while.
|
||
|
apb
|
a7eb98960f | Part of the new infrastructure for building tzdata under src/public-domain/tz. | ||
|
apb
|
dd837652ad | Adapt to the new source location under src/public-domain/tz. | ||
|
apb
|
1528d314bb | Add infrastructure for building tzdata under src/external/public-domain/tz. | ||
|
apb
|
102b42707c |
Copy src/share/zoneinfo/tzdata2netbsd (revision 1.5) to
src/external/public-domain/tz/tzdata2netbsd. This is a verbatim copy, as part of moving the zoneinfo sources in the NetBSD tree. It will need to be edited before it works. |
||
|
apb
|
6fcb06fd20 |
Copy src/share/zoneinfo/Makefile (revision 1.47) to
src/external/public-domain/tz/share/zoneinfo/Makefile. This is a verbatim copy, as part of moving the zoneinfo sources in the NetBSD tree. It will need to be edited before it works. |
||
|
apb
|
b10f80964b |
Import tzdata2014f from ftp://ftp.iana.org/tz/releases/tzdata2014f.tar.gz
and NEWS file from https://github.com/eggert/tz/raw/2014f/NEWS. NetBSD's tzdata code is being moved from src/share/zoneinfo to src/external/public-domain/tz/dist, to simplify future maintenance. This is the same version of tzata that was previously imported to src/share/zoneinfo. The NEWS file has been added to the import, although it is not distributed in the tzdata2014f.tar.gz file. |
||
|
martin
|
7a16006d41 | Try to avoid using float constants out of range | ||
|
christos
|
b8f0a3c0e7 |
change CC to HOST_CC to avoid trying to find <stdarg.h> in an unpopulated
DSTDIR. |
||
|
dsl
|
f00ab5270c | Add all: and dependall: tatgets so that sqlite3.pc actually gets built. | ||
|
christos
|
3053583861 | auto-generate so that it does not get out of sync again. | ||
|
christos
|
7cc8d35eaa | use the constant definition | ||
|
martin
|
884ddc8c02 | Fix bogus #ifdef __vax__ | ||
|
christos
|
1e27fa8ff1 | bump | ||
|
christos
|
9ea7afbfdb | merge conflicts. | ||
|
christos
|
24a762e46a |
from www.sqlite.org: Changes since 3.6.9:
2014-02-11 - Release 3.8.3.1
SQLite version 3.8.3.1 fixes a bug present in versions 3.8.1, 3.8.2 and 3.8.3 that can cause queries to omit valid out rows. Upgrading from those versions is recommended.
The problem only comes up if SQLite is compiled with either the SQLITE_ENABLE_STAT3 or SQLITE_ENABLE_STAT4 compile-time options. In that case, if a query has a WHERE clause that contains expressions like this:
WHERE (expr1 OR expr2 OR ... OR exprN) AND column IS NOT NULL
Where all of expr1 through exprN are suitable for use by indexes, then during query planning SQLite might mistakenly converted the "column IS NOT NULL" term into "column>NULL". But the latter term is never true, and so the query would return no rows.
The trouble ticket for this bug is [4c86b126f2]. It is recommended that all users upgrade to avoid this problem.
2014-02-03 - Release 3.8.3
SQLite version 3.8.3 is a regularly scheduled maintenance release. Upgrading from the previous release is optional.
The most visible change in version 3.8.3 is the addition of support for common table expressions. It is now possible to write a single SELECT statement that will query a tree or graph, using either a depth-first or a breadth-first search. A single SQLite query will even solve Sudoku puzzles or compute the Mandelbrot set. As part of this change, SQLite now accepts a VALUES clause anyplace that a SELECT statement is valid.
This release also includes many small performance enhancements which should give a small speed boost to legacy applications. And there are other minor enhancements such as the addition of the printf() SQL function. See the change log for details.
2013-12-06 - Release 3.8.2
SQLite version 3.8.2 is a regularly scheduled maintenance release. Upgrading from the previous release is optional.
Version 3.8.2 adds support for WITHOUT ROWID tables. This is a significant extension to SQLite. Database files that contain WITHOUT ROWID tables are not readable or writable by prior versions of SQLite, however databases that do not use WITHOUT ROWID tables are fully backwards and forwards compatible.
The 3.8.2 release contains a potentially incompatible change. In all prior versions of SQLite, a cast from a very large positive floating point number into an integer resulted in the most negative integer. In other words, CAST(+99.9e99 to INT) would yield -9223372036854775808. This behavior came about because it is what x86/x64 hardware does for the equivalent cast in the C language. But the behavior is bizarre. And so it has been changed effective with this release so that a cast from a floating point number into an integer returns the integer between the floating point value and zero that is closest to the floating point value. Hence, CAST(+99.9e99 to INT) now returns +9223372036854775807. Since routines like sqlite3_column_int64() do an implicit cast if the value being accessed is really a floating point number, they are also affected by this change.
Besides the two changes mentioned above, the 3.8.2 release also includes a number of performance enhancements. The skip-scan optimization is now available for databases that have been processed by ANALYZE. Constant SQL functions are now factored out of inner loops, which can result in a significant speedup for queries that contain WHERE clause terms like "date>datetime('now','-2 days')". And various high-runner internal routines have been refactored for reduced CPU load.
2013-10-17 - Release 3.8.1
SQLite version 3.8.1 is a regularly scheduled maintenance release. Upgrading from the previous release is optional, though you should upgrade if you are using partial indices as there was a bug related to partial indices in the previous release that could result in an incorrect answer for count(*) queries.
The next generation query planner that was premiered in the previous release continues to work well. The new query planner has been tweaked slightly in the current release to help it make better decisions in some cases, but is largely unchanged. Two new SQL functions, likelihood() and unlikely(), have been added to allow developers to give hints to the query planner without forcing the query planner into a particular decision.
Version 3.8.1 is the first SQLite release to take into account the estimated size of table and index rows when choosing a query plan. Row size estimates are based on the declared datatypes of columns. For example, a column of type VARCHAR(1000) is assumed to use much more space than a column of type INT. The datatype-based row size estimate can be overridden by appending a term of the form "sz=NNN" (where NNN is the average row size in bytes) to the end of the sqlite_stat1.stat record for a table or index. Currently, row sizes are only used to help the query planner choose between a table or one of its indices when doing a table scan or a count(*) operation, though future releases are likely to use the estimated row size in other contexts as well. The new PRAGMA stats statement can be used to view row size estimates.
Version 3.8.1 adds the SQLITE_ENABLE_STAT4 compile-time option. STAT4 is very similar to STAT3 in that it uses samples from indices to try to guess how many rows of the index will be satisfy by WHERE clause constraints. The difference is that STAT4 samples all columns of the index whereas the older STAT3 only sampled the left-most column. Users of STAT3 are encouraged to upgrade to STAT4. Application developers should use STAT3 and STAT4 with caution since both options, by design, violate the query planner stability guarantee, making it more difficult to ensure uniform performance is widely-deployed and mass-produced embedded applications.
2013-09-03 - Release 3.8.0.2
SQLite version 3.8.0.2 contains a one-line fix to a bug in the new optimization that tries to omit unused LEFT JOINs from a query.
2013-08-29 - Release 3.8.0.1
SQLite version 3.8.0.1 fixes some obscure bugs that were uncovered by users in the 3.8.0 release. Changes from 3.8.0 are minimal.
2013-08-26 - Release 3.8.0
Do not fear the zero!
SQLite version 3.8.0 might easily have been called "3.7.18" instead. However, this release features the cutover of the next generation query planner or NGQP, and there is a small chance of breaking legacy programs that rely on undefined behavior in previous SQLite releases, and so the minor version number was incremented for that reason. But the risks are low and there is a query planner checklist is available to application developers to aid in avoiding problems.
SQLite version 3.8.0 is actually one of the most heavily tested SQLite releases ever. Thousands and thousands of beta copies have be downloaded, and presumably tested, and there have been no problem reports.
In addition to the next generation query planner, the 3.8.0 release adds support for partial indices, as well as several other new features. See the change log for further detail.
2013-05-20 - Release 3.7.17
SQLite version 3.7.17 is a regularly schedule maintenance release. Visit the change log for a full explanation of the changes in this release.
There are many bug fixes in version 3.7.17. But this does not indicate that 3.7.16 was a problematic release. All of the bugs in 3.7.17 are obscure and are unlikely to impact any particular application. And most of the bugs that are fixed in 3.7.17 predate 3.7.16 and have been in the code for years without ever before being noticed. Nevertheless, due to the large number of fixes, all users are encouraged to upgrade when possible.
2013-04-12 - Release 3.7.16.2
SQLite version 3.7.16.2 fixes a long-standing flaw in the Windows OS interface that can result in database corruption under a rare race condition. See http://www.sqlite.org/src/info/7ff3120e4f for a full description of the problem.
As far as we know, this bug has never been seen in the wild. The problem was discovered by the SQLite developers while writing stress tests for a separate component of SQLite. Those stress tests have not yet found any problems with the component they were intended to verify, but they did find the bug which is the subject of this patch release.
Other than updates to version numbers, the only difference between this release and 3.7.16.1 is a two-character change in a single identifier, which is contained in the windows-specific OS interface logic. There are no changes in this release (other than version numbers) for platforms other than Windows.
2013-03-29 - Release 3.7.16.1
SQLite version 3.7.16.1 is a bug fix release that fixes a few problems that were present in the previous releases.
The primary motivation for version 3.7.16.1 is to fix a bug in the query optimizer that was introduced as part of version 3.7.15. The query optimizer was being a little overzealous in optimizing out some ORDER BY clauses, which resulted in sorting being omitted on occasions where sorting is required to get the correct answer. See ticket a179fe7465 for details.
In addition to the ORDER BY fix, several other patches to fix obscure (and mostly harmless) bugs and to fix spelling errors in source code comments are also included in this release.
2013-03-18 - Release 3.7.16
SQLite version 3.7.16 is a regularly scheduled release of SQLite. This release contains several language enhancements and improvements to the query optimizer. A list of the major enhancements and optimizations can be see on the change log.
There was one important bug fix (see Ticket fc7bd6358f) that addresses an incorrect query result that could have occurred in a three-way join where the join constraints compared INTEGER columns to TEXT columns. This issue had been in the code for time out of mind and had never before been reported, so we surmise that it is very obscure. Nevertheless, all users are advised to upgrade to avoid any future problems associated with this issue.
2013-01-09 - Release 3.7.15.2
SQLite version 3.7.15.2 is a patch release that fixes a single bug that was introduced in version version 3.7.15. The fix is a 4-character edit to a single line of code. Other than this 4-character change and the update of the version number, nothing has changed from version 3.7.15.1.
2012-12-19 - Release 3.7.15.1
SQLite version 3.7.15.1 is a patch release that fixes a single bug that was introduced in version version 3.7.15. The fix involved changing two lines of code and adding a single assert(). This release also includes some new test cases to prevent a regression of the bug, and the version number is increased, of course. But otherwise, nothing has changed from version 3.7.15.
2012-12-12 - Release 3.7.15
SQLite version 3.7.15 is a regularly schedule release of SQLite. This release contains several improvements to the query planner and optimizer and one important bug fix. This is the first release to officially support Windows 8 Phone.
The important bug fix is a problem that can lead to segfaults when using shared cache mode on a schema that contains a COLLATE operator within a CHECK constraint or within a view. Collating functions are associated with individual database connections. But a pointer to the collating function was also being cached within expressions. If an expression was part of the schema and contained a cached collating function, it would point to the collating function in the database connection that originally parsed the schema. If that database connection closed while other database connections using the same shared cache continued to operate, they other database connections would try to use the deallocated collating function in the database connection that closed. The fix in version 3.7.15 was to not cache collating function pointers in the expression structure but instead look them up each time a new statement is prepared.
This release also contains some important enhancements to the query planner which should (we hope) make some queries run faster. The enhancements include:
When doing a full-table scan, try to use an index instead of the original table, under the theory that indices contain less information and are thus smaller and hence require less disk I/O to scan.
Enhance the IN operator to allow it to make use of indices that have numeric affinity.
Do a better job of recognizing when an ORDER BY clause can be implemented using indices - especially in cases where the ORDER BY clause contains terms from two or more tables in a join.
2012-10-04 - Release 3.7.14.1
SQLite version 3.7.14.1 is a patch release. Changes from the baseline version 3.7.14 are minimal and are restricted to fixing three bugs.
One of the fixed bugs is a long-standing issue with the TCL interface. Another is an external compiler bug that SQLite merely works around and that only comes up if you are using the VisualStudio-2012 compiler to generate WinRT applications on ARM with optimizations enabled. The third problem is an SQLite core bug, introduced in version 3.7.14, that can cause a segfault if a query contains a LEFT JOIN that contains an OR in the ON clause.
2012-09-03 - Release 3.7.14
SQLite version 3.7.14 is a regularly scheduled maintenance release of SQLite. The previous release continues to work well. Upgrading is optional.
Version 3.7.14 drops native support for OS/2. We are not aware of any active projects that were using SQLite on OS/2 and since the SQLite developers had no way of testing on OS/2 it seemed like it was time to simply remove the OS/2 code from the SQLite tree. If there are OS/2 projects out there that still need SQLite support, they can continue to maintain their own private VFS which can be linked to SQLite at start-time using the sqlite3_vfs_register() interface.
The sqlite3_close_v2() interface has been added. The sqlite3_close_v2() interface differs from sqlite3_close() in that it is designed to work better for host language that use a garbage collector. With the older sqlite3_close() interface, the associated prepared statements and sqlite3_backup objects must be destroyed before the database connection. With the newer sqlite3_close_v2() interface, the objects can be destroyed in any order.
This release also includes performance improvements to the sort algorithm that is used to implement ORDER BY and CREATE INDEX. And the query planner has been enhanced to better use covering indices on queries that use OR terms in the WHERE clause.
2012-06-11 - Release 3.7.13
SQLite version 3.7.13 adds support for WinRT and metro style applications for Microsoft Windows 8. The 3.7.13 release is coming sooner than is usual after the previous release in order to get this new capability into the hands of developers. To use SQLite in a metro style application, compile with the -DSQLITE_OS_WINRT flag. Because of the increased application security and safety requirements of WinRT, all database filenames should be full pathnames. Note that SQLite is not capable of accessing databases outside the installation directory and application data directory. This restriction is another security and safety feature of WinRT. Apart from these restrictions, SQLite should work exactly the same on WinRT as it does on every other system.
Also in this release: when a database is opened using URI filenames and the mode=memory query parameter then the database is an in-memory database, just as if it had been named ":memory:". But, if shared cache mode is enabled, then all other database connections that specify the same URI filename will connect to the same in-memory database. This allows two or more database connections (in the same process) to share the same in-memory database.
This release also includes some corner-case performance optimizations that are obscure yet significant to an important subset of SQLite users. Getting these performance optimizations into circulation quickly is yet another reason for making this release so soon following the previous.
The next release of SQLite is scheduled to occur after the usual 2 or 3 month interval.
2012-05-22 - Patch Release 3.7.12.1
SQLite version 3.7.12.1 is a patch release for version 3.7.12 that fixes a bug that was introduced in version 3.7.12 and that can cause a segfault for certain obscure nested aggregate queries. There are very few changes in 3.7.12.1, and upgrading is only needed for applications that do nested aggregate queries.
2012-05-14 - Version 3.7.12
SQLite version 3.7.12 is a regularly scheduled maintenance release. This release contains several new optimizations and bug fixes and upgrading is recommended. See the change summary for details.
2012-03-20 - Version 3.7.11
SQLite version 3.7.11 is a regularly scheduled maintenance release which was rushed out early due to a bug in the query optimizer introduced in the previous release. The bug is obscure - it changes a LEFT JOIN into an INNER JOIN in some cases when there is a 3-way join and OR terms in the WHERE clause. But it was considered serious enough to rush out a fix. Apart from this one problem, SQLite version 3.7.10 has not given any trouble. Upgrading to version 3.7.11 from versions 3.7.6.3, 3.7.7, 3.7.7.1, 3.7.8, or 3.7.9 is optional. Upgrading from other releases, including the previous release 3.7.10, is recommended.
Other enhancements found in this release are enumerated in the change log.
2012-01-16 - Version 3.7.10
SQLite version 3.7.10 is a regularly scheduled maintenance release. Upgrading from version 3.7.6.3, 3.7.7, 3.7.7.1, 3.7.8, or 3.7.9 is optional. Upgrading from other releases is recommended.
The SQLITE_CONFIG_PCACHE mechanism has been replaced with SQLITE_CONFIG_PCACHE2. If you do not know what this mechanism is (it is an extreme corner-case and is seldom used) then this change will not effect you in the least.
The default schema format number for new database files has changed from 1 to 4. SQLite has been able to generate and read database files using schema format 4 for six years. But up unto now, the default schema format has been 1 so that older versions of SQLite could read and write databases generated by newer versions of SQLite. But those older versions of SQLite have become so scarce now that it seems reasonable to make the new format the default.
SQLite is changing some of the assumptions it makes above the behavior of disk drives and flash memory devices during a sudden power loss. This change is completely transparent to applications. Read about the powersafe overwrite property for additional information.
Lots of new interfaces have been added in this release:
sqlite3_db_release_memory()
PRAGMA shrink_memory
sqlite3_db_filename()
sqlite3_stmt_busy()
sqlite3_uri_boolean()
sqlite3_uri_int64()
The PRAGMA cache_size statement has been enhanced. Formerly, you would use this statement to tell SQLite how many pages of the database files it should hold in its cache at once. The total memory requirement would depend on the database page size. Now, if you give PRAGMA cache_size a negative value -N, it will allocate roughly N kibibytes of memory to cache, divided up according to page size. This enhancement allows programs to more easily control their memory usage.
There have been several obscure bug fixes. One noteworthy bug, ticket ff5be73dee, could in theory result in a corrupt database file if a power loss occurred at just the wrong moment on an unusually cantankerous disk drive. But that is mostly a theoretical concern and is very unlikely to happen in practice. The bug was found during laboratory testing and has never been observed to occur in the wild.
2011-11-01 - Version 3.7.9
SQLite version 3.7.9 is a regularly scheduled maintenance release. Upgrading from version 3.7.6.3, 3.7.7, 3.7.7.1, and 3.7.8 is optional. Upgrading from other versions is recommended.
The SQLITE_ENABLE_STAT2 compile-time option is now a no-op. The enhanced query-planner functionality formerly available using SQLITE_ENABLE_STAT2 is now available through SQLITE_ENABLE_STAT3. The enhanced query planning is still disabled by default. However, future releases of SQLite might convert STAT3 from an enable-option to a disable-option so that it is available by default and is only omitted upon request.
The FTS4 full-text search engine has been enhanced such that tokens in the search string that begin with "^" must be the first token in their respective columns in order to match. Formerly, "^" characters in the search string were simply ignored. Hence, if a legacy application was including "^" characters in FTS4 search strings, thinking that they would always be ignored, then those legacy applications might break with this update. The fix is simply remove the "^" characters from the search string.
See the change summary for additional changes associated with this release.
2011-September-19 - Version 3.7.8
SQLite version 3.7.8 is a quarterly maintenance release. Upgrading from versions 3.7.6.3, 3.7.7, or 3.7.7.1 is optional. Upgrading from other versions is recommended.
This release features a new "external merge sort" algorithm used to implement ORDER BY and GROUP BY and also to presort the content of an index for CREATE INDEX. The new algorithm does approximately the same number of comparisons and I/Os as before, but the I/Os are much more sequential and so runtimes are greatly reduced when the size of the set being sorted is larger than the filesystem cache. The performance improvement can be dramatic - orders of magnitude faster for large CREATE INDEX commands. On the other hand, the code is slightly slower (1% or 2%) for a small CREATE INDEX. Since CREATE INDEX is not an operation that commonly occurs on a speed-critical path, we feel that this tradeoff is a good one. The slight slowdown for small CREATE INDEX statements might be recovered in a future release. ORDER BY and GROUP BY operations should now be faster for all cases, large and small.
The query planner has been enhanced to do a better job of handling the DISTINCT keyword on SELECT statements.
There has been a lot of work on the default VFSes. The unix VFS has been enhanced to include more overrideable system calls - a feature requested by Chromium to make it easier to build SQLite into a sandbox. The windows VFS has been enhanced to be more resistant to interference from anti-virus software.
Every version of SQLite is better tested than the previous, and 3.7.8 is no exception to this rule. Version 3.7.8 has been used internally by the SQLite team for mission critical functions and has performed flawlessly. And, of course, it passes our rigorous testing procedures with no problems detected. Version 3.7.8 is recommended for all new development.
2011-06-28 - Version 3.7.7.1
SQLite version 3.7.7.1 adds a one-line bug fix to 3.7.7 to fix a problem causing PRAGMA case_sensitive_like statements compiled using the legacy sqlite3_prepare() interface to fail with an SQLITE_SCHEMA error. Because sqlite3_exec() uses sqlite3_prepare() internally, the problem also affects sqlite3_exec().
Upgrading from 3.7.7 is only required for applications that use "PRAGMA case_sensitive_like" and the sqlite3_prepare() (or sqlite3_exec()) interface.
2011-06-24 - Version 3.7.7
SQLite version 3.7.7 is a regularly scheduled bi-monthly maintenance release. Upgrading from version 3.7.6.3 is optional. Upgrading from all prior releases is recommended.
This release adds support for naming database files using URI filenames. URI filenames are disabled by default (for backwards compatibility) but applications are encouraged to enable them since incompatibilities are likely to be exceedingly rare and the feature is useful. See the URI filename documentation for details.
Most of the other enhancements in this release involve virtual tables. The virtual table interface has been enhanced to support SAVEPOINT and ON CONFLICT clause processing, and the built-in RTREE and FTS3/FTS4 have been augmented to take advantage of the new capability. This means, for example, that it is now possible to use the REPLACE command on FTS3/FTS4 and RTREE tables.
The FTS4 full-text index extension has been enhanced to support the FTS4 prefix option and the FTS4 order option. These two enhancements are provided in support of search-as-you-type interfaces where search results begin to appear after the first keystroke in the "search" box and are refined with each subsequent keystroke. The way this is done is to do a separate full-text search after each key stroke, and add the "*" wildcard at the end of the word currently being typed. So, for example, if the text typed so far is "fast da" and the next character typed is "t", then the application does a full-text search of the pattern "fast dat*" and displays the results. Such capability has always existed. What is new is that the FTS4 prefix option allows the search to be very fast (a matter of milliseconds) even for difficult cases such as "t*" or "th*".
There has been a fair amount of work done on the FTS4 module for this release. But the core SQLite code has changed little and the previous release has not given any problems, so we expect this to be a very stable release.
2011-05-19 - Version 3.7.6.3
SQLite version 3.7.6.3 is a patch release that fixes a single bug associated with WAL mode. The bug has been in SQLite ever since WAL was added, but the problem is very obscure and so nobody has noticed before now. Nevertheless, all users are encouraged to upgrade to version 3.7.6.3 or later.
The bug is this: If the cache_size is set very small (less than 10) and SQLite comes under memory pressure and if a multi-statement transaction is started in which the last statement prior to COMMIT is a SELECT statement and if a checkpoint occurs right after the transaction commit, then it might happen that the transaction will be silently rolled back instead of being committed.
The default setting for cache_size is 2000. So in most situations, this bug will never appear. But sometimes programmers set cache_size to very small values on gadgets and other low-memory devices in order to save memory space. Such applications are vulnerable. Note that this bug does not cause database corruption. It is as if ROLLBACK were being run instead of COMMIT in some cases.
Bug Details
Transactions commit in WAL mode by adding a record onto the end of the WAL (the write-ahead log) that contains a "commit" flag. So to commit a transaction, SQLite takes all the pages that have changed during that transaction, appends them to the WAL, and sets the commit flag on the last page. Now, if SQLite comes under memory pressure, it might try to free up memory space by writing changed pages to the WAL prior to the commit. We call this "spilling" the cache to WAL. There is nothing wrong with spilling cache to WAL. But if the memory pressure is severe, it might be that by the time COMMIT is run, all changed pages for the transaction have already been spilled to WAL and there are no pages left to be written to WAL. And with no unwritten pages, there was nothing to put the commit flag on. And without a commit flag, the transaction would end up being rolled back.
The fix to this problem was that if all changed pages has already been written to the WAL when the commit was started, then page 1 of the database will be written to the WAL again, so that there will always be a page available on which to set the commit flag.
2011-04-17 - Version 3.7.6.2
SQLite version 3.7.6.2 adds a one-line bug fix to 3.7.6.1 that enables pthreads to work correctly on NetBSD. The problem was a faulty function signature for the open system call. The problem does not appear to have any adverse impact on any system other than NetBSD.
Upgrading from version 3.7.6.1 is only needed on NetBSD.
2011-04-13 - Version 3.7.6.1
SQLite version 3.7.6.1 fixes a single bug in 3.7.6 that can cause a segfault if SQLITE_FCNTL_SIZE_HINT is used on a unix build that has SQLITE_ENABLE_LOCKING_MODE set to 0 and is compiled with HAVE_POSIX_FALLOCATE.
Upgrading from 3.7.6 is only needed for users effected by the configuration-specific bug described above. There are no other changes to the code.
2011-04-12 - Version 3.7.6
SQLite version 3.7.6 is a regularly scheduled bi-monthly maintenance release of SQLite. Upgrading from version 3.7.5 is optional. Upgrading releases prior to 3.7.5 is recommended.
2011-02-01 - Version 3.7.5
SQLite version 3.7.5 is a regularly scheduled bi-monthly maintenance release of SQLite. Due to the discovery and fix of an obscure bug that could cause database corruption, upgrading from all prior releases of SQLite is recommended. This bug was found during code review and has not been observed in the wild.
This release adds new opcodes for the sqlite3_db_status() interface that allow more precise measurement of how the lookaside memory allocator is performing, which can be useful for tuning in applications with very tight memory constraints.
The sqlite3_vsnprintf() interface was added. This routine is simply a varargs version of the long-standing sqlite3_snprintf() interface.
The output from sqlite3_trace() interface has been enhanced to work better (and faster) in systems that use recursive extensions such as FTS3 or RTREE.
Testing with Valgrind shows that this release of SQLite is about 1% or 2% faster than the previous release for most operations.
A fork of the popular ADO.NET adaptor for SQLite known as System.Data.SQLite is now available on http://System.Data.SQLite.org/. The originator of System.Data.SQLite, Robert Simpson, is aware of this fork, has expressed his approval, and has commit privileges on the new Fossil repository. The SQLite development team intends to maintain System.Data.SQLite moving forward.
2010-12-08 - Version 3.7.4
SQLite version 3.7.4 is a regularly scheduled bi-monthly maintenance release of SQLite. Upgrading from version 3.7.2 and version 3.7.3 is optional. Upgrading from all other SQLite releases is recommended.
This release features full-text search enhancements. The older FTS3 virtual table is still fully supported, and should also run faster. In addition, the new FTS4 virtual table is added. FTS4 follows the same syntax as FTS3 but holds additional metadata which facilitates some performance improvements and more advanced matchinfo() output. Look for further full-text search enhancements in subsequent releases.
Also in this release, the EXPLAIN QUERY PLAN output has been enhanced and new documentation is provided so that application developers can more easily understand how SQLite is performing their queries.
Thanks to an account from the folks at http://www.devio.us/, OpenBSD has been added to the list of platforms upon which we test SQLite prior to every release. That list of platforms now includes:
Linux x86 & x86_64
MacOS 10.5 & 10.6
MacOS 10.2 PowerPC
WinXP and Win7
Android 2.2
OpenBSD 4.7
The previous release of SQLite (version 3.7.3) has proven to be very robust. The only serious issue discovered was ticket 80ba201079 that describes an incorrect query result that can occur under very unusual circumstances. The ticket description contains details of the problem. Suffice it to say here that the problem is very obscure and is unlikely to effect most applications and so upgrading is optional. The problem is fixed, of course, in this release.
2010-October-08 - Version 3.7.3
SQLite version 3.7.3 is a regularly scheduled bi-monthly maintenance release of SQLite. Upgrading from version 3.7.2 is optional. Upgrading from all other releases is recommended.
This release adds two new interfaces (really just variations on existing interfaces). The sqlite3_create_function_v2() interface adds a destructor for the application-data pointer. The new sqlite3_soft_heap_limit64() interface allows the soft heap limit to be set to a value greater than 231.
The RTREE extension has been enhanced with the ability to have an application-defined query region. This might be used, for example, to locate all objects within the field of view of a camera.
The 3.7.3 release also includes some performance enhancements, including query planner improvements, documentation updates, and fixes to some very obscure bugs.
2010-August-24 - Version 3.7.2
SQLite version 3.7.2 fixes a long-standing bug that can cause the database free-page list to go corrupt if incremental_vacuum is used multiple times to partially reduce the size of a database file that contains many hundreds of unused database pages. The original bug reports together with links to the patch that fixes it can be seen here.
This bug has been in the code for at least a year and possibly longer. The bug has nothing to do with the versions 3.7.1 or 3.7.0 or any other recent release. The fact that the bug was discovered (and fixed) within hours of the 3.7.1 release is purely a coincidence.
The bug is impossible to hit without using incremental_vacuum and is very difficult to hit even with incremental_vacuum. And the kind of corruption that the bug causes can usually be fixed simply by running VACUUM. Nevertheless, because the bug can result in database corruption, it is recommended that all SQLite users upgrade to version 3.7.2 or later.
2010-August-23 - Version 3.7.1
SQLite version 3.7.1 is a stabilization release for the 3.7.x series. Other than the filesize-in-header bug that was fixed in version 3.7.0.1, no major problems have been seen in 3.7.0. Some minor corner-case performance regressions have been fixed. A typo in the OS/2 interface has been repaired.
A biggest part of the 3.7.1 release is a cleanup and refactoring of the pager module within SQLite. This refactoring should have no application-visible effects. The purpose was to reorganize the code in ways that make it easier to prove correctness.
The 3.7.1 release adds new experimental methods for obtained more detailed memory usage information and for controlling database file fragmentation. And the query planner now does a better job of optimizing the LIKE and GLOB operators.
This release increases the maximum size of database pages from 32KiB to 64KiB. A database with 64KiB pages will not be readable or writable by older versions of SQLite. Note that further increases in page size are not feasible since the file format uses 16-bit offsets to structures within each page.
2010-August-04 - Version 3.7.0.1
SQLite version 3.7.0.1 is a patch release to fix a bug in the new filesize-in-header feature of the SQLite file format that could cause database corruption if the same database file is written alternately with version 3.7.0 and version 3.6.23.1 or earlier. A performance regression was also fixed in this release.
2010-07-22 - Version 3.7.0
SQLite version 3.7.0 is a major release of SQLite that features a new transaction control mechanism using a write-ahead log or WAL. The traditional rollback-journal is still used as the default so there should be no visible change for legacy programs. But newer programs can take advantage of improved performance and concurrency by enabling the WAL journaling mode.
SQLite version 3.7.0 also contains some query planner enhancements and a few obscure bug fixes, but the only really big change is the addition of WAL mode.
2010-03-30 - Version 3.6.23.1
SQLite version 3.6.23.1 is a patch release to fix a bug in the offsets() function of FTS3 at the request of the Mozilla.
2010-03-09 - Version 3.6.23
SQLite version 3.6.23 is a regular bimonthly release of SQLite. Upgrading from the prior release is purely optional.
This release contains new pragmas: the secure_delete pragma, and the compile_options pragma. There are a new SQL functions: sqlite_compileoption_used() and sqlite_compileoption_get(). New C/C++ interfaces: sqlite3_compileoption_used(), sqlite3_compileoption_get(), SQLITE_CONFIG_LOG, and sqlite3_log().
This release also includes several minor bug fixes and performance improvements. Support for SQLITE_OMIT_FLOATING_POINT is enhanced. There are on-going improvements to FTS3.
The ".genfkey" command in the Command Line Interface has been removed. SQLite has supported standard SQL foreign key constraints since version 3.6.19 and so the ".genfkey" command was seen as an anachronism.
2010-01-06 - Version 3.6.22
SQLite version 3.6.22 is a bug-fix release. Two bugs have been fixed that might cause incorrect query results.
Ticket 31338dca7e describes a problem with queries that have a WHERE clause of the form (x AND y) OR z where x and z come from one table of a join and y comes from a different table.
Ticket eb5548a849 describes a problem where the use of the CAST operator in the WHERE clause can lead to incorrect results if the column being cast to a new datatype is also used in the same WHERE clause without being cast.
Both bugs are obscure, but because they could arise in an application after deployment, it is recommended that all applications upgrade SQLite to version 3.6.22.
This release also includes other minor bug fixes and performance enhancements, especially in the FTS3 extension.
2009-12-07 - Version 3.6.21
SQLite version 3.6.21 focuses on performance optimization. For a certain set of traces, this version uses 12% fewer CPU instructions than the previous release (as measured by Valgrind). In addition, the FTS3 extension has been through an extensive cleanup and rework and the sqlite3_trace() interface has been modified to insert bound parameter values into its output.
2009-11-04 - Version 3.6.20
SQLite version 3.6.20 is a general maintenance release. The query planner has been enhanced to work better with bound parameters in LIKE and GLOB operators and in range constraints and various minor bugs have been fixed. Upgrading from 3.6.19 is optional.
2009-10-14 - Version 3.6.19
SQLite version 3.6.19 adds native support for foreign key constraints, including deferred constraints and cascading deletes. Enforcement of foreign keys is disabled by default for backwards compatibility and must be turned on using the foreign_keys pragma.
Version 3.6.19 also adds support for the IS and IS NOT operators. Formerly, SQLite (as most other SQL database engines) supported IS NULL and IS NOT NULL. The IS and IS NOT operators are generalizations that allow the right-hand side to be an arbitrary expression. IS and IS NOT work the same as == (equals) and != (not equals) except that with IS and IS NOT the NULL values compare equal to one another.
2009-09-11 - Version 3.6.18
Beginning with this release, the SQLite source code is tracked and managed using the Fossil distributed configuration management system. SQLite was previously versioned using CVS. The entire CVS history has been imported into Fossil. The older CVS repository remains on the website but is read-only.
There are two major enhancements in SQLite version 3.6.18. The first is a series or refinements to the query planner that help SQLite to choose better plans for joins where in the past it was selecting suboptimal query plans. The SQLITE_ENABLE_STAT2 compile-time option has been added to cause SQLite to collect histogram data on indices when the ANALYZE command is run. The use of histograms improve the query planning performance even more.
The second major enhancement is that SQLite now support recursive triggers. The older non-recursive behavior of triggers is still the default behavior. Recursive triggers are activated using the recursive_triggers pragma. In addition to allowing triggers to call themselves (either directly or indirectly) the new capability also fires DELETE triggers on rows that are removed from a table as a result of REPLACE conflict resolution processing.
Non-recursive triggers are still the default behavior since this is least likely to cause problems for existing applications. However, we anticipate that triggers will become recursive by default beginning with release 3.7.0. At that point, applications that want to continue using the older non-recursive trigger behavior will need to use the recursive_triggers pragma to disable recursive triggers.
This version of SQLite also contains bug fixes, though none of the bugs are serious and all are obscure, so upgrading is optional.
The SQLite core continues to have 100% branch test coverage and so despite the many changes in this release, the developers believe that this version of SQLite is stable and ready for production use.
2009-08-10 - Version 3.6.17
This is a monthly maintenance release with a focus of bug fixes, performance improvements, and increased test coverage. This is the first release of SQLite since 100% branch test coverage was achieved on the SQLite core.
In addition, a new interface sqlite3_strnicmp() is provided for the convenience of extension writers.
None of the bugs fixed in this release are serious. All bugs are obscure. Upgrading is optional.
2009-07-25 - 100% Branch Test Coverage
A subset of the TH3 test suite was measured by gcov to provide 100% branch test coverage over the SQLite core (exclusive of the VFS backend and of extensions such as FTS3 and RTREE) when compiled for SuSE 10.1 Linux on x86. The SQLite developers pledge to maintain branch test coverage at 100% in all future releases. Ongoing work will strive for 100% branch test coverage on the operating-system backends and extensions as well.
2009-06-27 - Version 3.6.16
SQLite version 3.6.16 is another general maintenance release containing performance and robustness enhancements. A single notable bug was fixed (ticket #3929). This bug cause cause INSERT or UPDATE statements to fail on indexed tables that have AFTER triggers that modify the same table and index.
2009-06-15 - Version 3.6.15
SQLite version 3.6.15 is a general maintenance release containing performance and robustness enhancements and fixes for various obscure bugs.
2009-05-25 - Version 3.6.14.2
SQLite version 3.6.14.2 fixes an obscure bug in the code generator (ticket #3879) section of SQLite which can potentially cause incorrect query results. The changes from the prior release consist of only this one bug fix, check-in [6676] and a change to the version number text.
The bug was introduced in version 3.6.14. It is recommended that users of version 3.6.14 and 3.6.14.1 upgrade to this release. Applications are unlikely to hit this bug, but since it is difficult to predict which applications might hit it and which might not, we recommend that all users of 3.6.14 and 3.5.14.1 upgrade to this release.
2009-05-19 - Version 3.6.14.1
SQLite version 3.6.14.1 is a patch release to version 3.6.14 with minimal changes that fixes three bugs. Upgrading is only necessary for users who are impacted by one or more of those bugs.
2009-05-07 - Version 3.6.14
SQLite version 3.6.14 provides new performance enhancements in the btree and pager layers and in the query optimizer. Certain workloads can be as much as twice as fast as the previous release, though 10% faster is a more typical result.
Queries against virtual tables that contain OR and IN operators in the WHERE clause are now able to use indexing.
A new optional asynchronous I/O backend is available for unix and windows. The asynchronous backend gives the illusion of faster response time by pushing slow write operations into a background thread. The tradeoff for faster response time is that more memory is required (to hold the content of the pending writes) and if a power failure or program crash occurs, some transactions that appeared to have committed might end up being rolled back upon restart.
This release also contains many minor bug fixes, documentation enhancements, new test cases, and cleanups and simplifications to the source code.
There is no compelling reason to upgrade from versions 3.6.12 or 3.6.13 if those prior versions are working. Though many users may benefit from the improved performance.
|
||
|
martin
|
33a57db067 |
Backout libm dependency here as well (assuming it was meant for the
backed-out use of floor() I added/removed yesterday) |
||
|
martin
|
cbad08c3fb | Backout previous | ||
|
matt
|
d8eebedb0c | Link against libm | ||
|
martin
|
9a9df90953 |
When converting long double values to decimal, convert to int via a call
to floor(), so the conversion does not depend on current rounding mode. Fixes PR port-sparc64/47535. |
||
|
njoly
|
c15d05d6e1 | Fix unknown Fi macro. | ||
|
christos
|
2f4f3871a1 | now that I know how to escape a period, nothing can stop me :-) | ||
|
wiz
|
e4bf1b2ca5 |
Fix some obvious problems and remove trailing whitespace.
Use more markup. |
||
|
christos
|
bafb9c842e | noman is no more | ||
|
christos
|
b6b2f24e70 | convert to mdoc | ||
|
christos
|
2136559eac | from ubuntu-9.10 | ||
|
wiz
|
d0df7c443e |
Make HAVE_* define match what configure finds.
In particular, this enables usleep(3) (compared to using sleep(3) before). ok joerg@ |
||
|
jdc
|
b8c75e7dab |
Determine WORDS_BIGENDIAN at build time, rather than hardcoding it to 0.
Makes liblzma work on sparc64 (and probably other big endian hosts too). Add a note to the import script. |