From: Jan Nijtmans <jan.nijtmans@gmail.com>
To: cygwin-announce@cygwin.com
Subject: Updated: sqlite3-3.8.2-3 for Cygwin/Cygwin64
Date: Fri, 10 Jan 2014 12:37:00 -0000 [thread overview]
Message-ID: <CAO1jNwvGUTc4D9NBLaG6iYMy+UYgX6cmGJjs0nXE1bh=dDyBYg@mail.gmail.com> (raw)
SQLite is a software library that implements a self-contained,
serverless, zero-configuration, transactional SQL database engine
Changes since 3.8.2-2
=====================
* Added full Unicode support to the sqlite3 utility, by linking it
with the icu extension statically. Therefore requires libicu as
additional dependency (for sqlite3 only, not for libsqlite3_0)
* Added "compress" and "uncompress" SQL functions to
sqlite3 utility. Therefore requires zlib0 as additional
dependancy (again: for sqlite3 only, not for libsqlite3_0)
* Add the build of new "tcl-sqlite3" package to the source
package (binaries not available yet).
* The following 5 bug-fixes, which are all backported from
SQLite 3.8.3 alpha (in chronological order):
- Fix "Array overrun in the skip-scan optimization"
See: <http://www.sqlite.org/src/info/520070ec7fbaac>
- Fix a bug in the shell ".import" command: Do not end the field
when an escaped double-quote occurs at the end of a CRNL line.
See: <http://www.sqlite.org/src/info/5e239ecda0>
- Fix the ".echo on" dot-command of the shell so that it echos
comments in addition to SQL statements and dot-commands
See: <http://www.sqlite.org/src/info/96397263f9>
- Correct the VFS name as reported by the file control when
explicitly using the 'win32-longpath' VFS.
See: <http://www.sqlite.org/src/info/c43b59dac1>
- Fix "SQLite3 temporary filename collision in worker processes":
See: <https://www.mail-archive.com/sqlite-users@sqlite.org/msg81284.html>
Regards,
Jan Nijtmans
reply other threads:[~2014-01-10 12:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAO1jNwvGUTc4D9NBLaG6iYMy+UYgX6cmGJjs0nXE1bh=dDyBYg@mail.gmail.com' \
--to=jan.nijtmans@gmail.com \
--cc=cygwin-announce@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).