Opened 8 years ago
Closed 8 years ago
#8716 closed enhancement (fixed)
sqlite-autoconf sqlite-doc 3160200 (3.16.2)
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | 8.0 |
Component: | BOOK | Version: | SVN |
Severity: | normal | Keywords: | |
Cc: |
Description ¶
New minor version
Change History (5)
comment:1 by , 8 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:2 by , 8 years ago
Summary: | sqlite-autoconf sqlite-doc 3160000 (3.16.0) → sqlite-autoconf sqlite-doc 3160100 (3.16.1) |
---|
comment:4 by , 8 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Summary: | sqlite-autoconf sqlite-doc 3160100 (3.16.1) → sqlite-autoconf sqlite-doc 3160200 (3.16.2) |
When a package is released, I've observed that the probability for another release soon after is much higher for some packages.
Now version 3.16.2.
- Fix the REPLACE statement for WITHOUT ROWID tables that lack secondary indexes so that it works correctly with triggers and foreign keys. This was a new bug caused by performance optimizations added in version 3.16.0. Ticket 30027b613b4
- Fix the sqlite3_value_text() interface so that it correctly translates content generated by zeroblob() into a string of all 0x00 characters. This is a long-standing issue discovered after the 3.16.1 release by OSS-Fuzz
- Fix the bytecode generator to deal with a subquery in the FROM clause that is itself a UNION ALL where one side of the UNION ALL is a view that contains an ORDER BY. This is a long-standing issue that was discovered after the release of 3.16.1. See ticket 190c2507.
- Adjust the sqlite3_column_count() API so it more often returns the same values for PRAGMA statements as it did in prior releases, to minimize disruption to applications that might be using that interface in unexpected ways.
Note:
See TracTickets
for help on using tickets.
Now version 3.16.1.
2017-01-03 (3.16.1)
2017-01-02 (3.16.0)