Re: [sqlite] Bug Report: https://www.sqlite.org/chronology.html out of date

I think it depends on what Tom means by the "latest release". The chronology shows the "latest" in chronological order. But the latest in chronological order is not necessary the same as the latest in logical order. In other words, perhaps Tom is assuming that release numbers are monotonically

Re: [sqlite] Bug Report: https://www.sqlite.org/chronology.html out of date

On 20 June 2017 at 07:55, Tom Ritter wrote: > In lieu of an official support RSS feed, > https://www.sqlite.org/chronology.html is used to detect new versions > of SQLite and how out of date the current one embedded in a product > is. It worked for the past several months, but now

[sqlite] UTF8-BOM not disregarded in CSV import

Hello all, Let me start off with my apologies if this is a documented issue; I did search the fossil tickets but did not find anything for “BOM”. As of SQLite 3.19.3, under `.mode csv` and with `.import ……`, SQLite3 includes a BOM (UTF-8) as part of the first column of the first record. IMHO,

[sqlite] Bug Report: https://www.sqlite.org/chronology.html out of date

In lieu of an official support RSS feed, https://www.sqlite.org/chronology.html is used to detect new versions of SQLite and how out of date the current one embedded in a product is. It worked for the past several months, but now this page is out of date. =) -tom

Re: [sqlite] How to search for fields with accents in UTF-8 data?

Thanks for the infos. __ If you reply to this email, your message will be added to the discussion below: http://sqlite.1065341.n5.nabble.com/How-to-search-for-fields-with-accents-in-UTF-8-data-tp96249p96294.html This email was sent by Winfried (via Nabble)