On 4/24/16, Richard Hipp <drh at sqlite.org> wrote:
>
> The problem is apparently caused by the optimization added by check-in
> https://www.sqlite.org/src/info/6df18e949d367629 on 2015-06-02 and
> first released in version 3.8.11 on 2015-07-27.
>

Ticket: https://www.sqlite.org/src/info/f7f8c97e97597
Fix: https://www.sqlite.org/src/info/ec215f94ac9748c0
-- 
D. Richard Hipp
drh at sqlite.org

Reply via email to