From: Jan Nijtmans <jan.nijtmans@gmail.com>
To: cygwin@cygwin.com
Subject: [ANNOUNCEMENT] [ANNOUNCEMENT] Updated: sqlite3-3.8.1-1 for Cygwin/Cygwin64
Date: Mon, 18 Nov 2013 15:02:00 -0000 [thread overview]
Message-ID: <announce.CAO1jNwtiF98u8FW2xM_uc2HkGHH63u8QGz9WDJmr8V+Szeo6tA@mail.gmail.com> (raw)
SQLite is a software library that implements a self-contained,
serverless, zero-configuration, transactional SQL database engine
Changes since 3.7.17-3
=====================
* Updated to upstream 3.8.1 release. Main new features:
* Partial indexes: <http://www.sqlite.org/partialindex.html>
* New query planner: <http://www.sqlite.org/queryplanner-ng.html>
* 3 new VFS's:
"win32" Old win32 implementation, which limits file
paths to 160 chars. Don't use it.
"win32-longpath" New win32 implementation, implemented
by SQLite dll. Not very well tested (on Cygwin).
"winnt": The same behavior as "win32-longpath", but implemented
by cygwin1.dll
* The "unix" VFS (the default) is rewritten following the SQLite
programming conventions. It should behave exactly the same
as the default "unix" VFS in SQLite 3.7.17-3:
The environment variable CYGWIN_SQLITE_LOCKING can be used
to specify which file locking is desired, "posix", "bsd", "dotfile"
or "winnt".
The default is "winnt".
* The dll is no longer built with SQLITE_TEMP_STORE=2, which was
a workaround for a SQLite bug. This bug should be fixed now.
If your queries are slower than before (however unlikely), see:
<http://www.sqlite.org/draft/queryplanner-ng.html#hazards>
--
Jan Nijtmans
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
reply other threads:[~2013-11-18 15:02 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=announce.CAO1jNwtiF98u8FW2xM_uc2HkGHH63u8QGz9WDJmr8V+Szeo6tA@mail.gmail.com \
--to=jan.nijtmans@gmail.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).