#7084: sqlite-autoconf-3090200 (3.9.2)
-------------------------+-------------------------
 Reporter:  fo           |      Owner:  blfs-book@…
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:  7.9
Component:  BOOK         |    Version:  SVN
 Severity:  normal       |   Keywords:
-------------------------+-------------------------
 [https://www.sqlite.org/2015/sqlite-autoconf-3090200.tar.gz]

 [https://www.sqlite.org/2015/sqlite-doc-3090200.zip]

 [https://www.sqlite.org/download.html]

 sqlite-autoconf-3090200.tar.gz  sha1:
 dae1ae5297fece9671ae0c434a7ecd0cda09c76a

 sqlite-doc-3090200.zip          sha1:
 31a2e8a845e24968ede785ec09e057514c3538fd

 [http://permalink.gmane.org/gmane.comp.db.sqlite.announce/52]

 {{{
 Version 3.9.2

 SQLite version 3.9.2 is now available on the SQLite website

      https://www.sqlite.org/

 Version 3.9.2 is a patch release that fixes two obscure bugs.  See the
 release notes (http://www.sqlite.org/releaselog/3_9_2.html) for details.
 Upgrading from version 3.9.1 is optional.

 ...

 --
 D. Richard Hipp
 drh <at> sqlite.org
 }}}

 [https://www.sqlite.org/releaselog/3_9_2.html]

 {{{
 SQLite Release 3.9.2 On 2015-11-03

  • Fix the schema parser so that it interprets certain (obscure and
    ill-formed) CREATE TABLE statements the same as legacy. Fix for
    ticket ac661962a2aeab3c331
  • Fix a query planner problem that could result in an incorrect answer
    due to the use of automatic indexing in subqueries in the FROM clause
    of a correlated scalar subqueries. Fix for ticket 8a2adec1.
  • SQLITE_SOURCE_ID: "2015-11-02 18:31:45
    bda77dda9697c463c3d0704014d51627fceee328"
  • SHA1 for sqlite3.c: 1c4013876f50bbaa3e6f0f98e0147c76287684c1

 ...
 }}}

--
Ticket URL: <http://wiki.linuxfromscratch.org/blfs/ticket/7084>
BLFS Trac <http://wiki.linuxfromscratch.org/blfs>
Beyond Linux From Scratch
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to