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

> Le 20 juin 2017 à 20:04, Scott Robison a écrit : > > Regardless, I prefer UTF-8 to UCS-2 / UTF-16. Microsoft has certainly > had time to make their interfaces more UTF-8 friendly. I just don't > think they get enough credit for committing to Unicode in an era when >

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

On Tue, Jun 20, 2017 at 8:17 AM, Olivier Mascia wrote: >> Le 20 juin 2017 à 15:24, R Smith a écrit : >> >> As an aside - I never understood the reasons for that. I get that Windows >> has a less "techy" clientèle than Linux for instance, and that the

Re: [sqlite] Possible issue with 3.19.3

On 6/20/17, Eric Sink wrote: > Greetings, > > Version 3.19.3 is yielding different results than previous releases for a > query in the Entity Framework Core test suite. > The results also differed from Postgres, which is our gold-standard. So, yes, it was a problem. The bug

Re: [sqlite] JSON1 extension & speed-up by using indices etc.?

> On Jun 20, 2017, at 12:48 AM, Robert M. Münch > wrote: > > Since at one point I know all the columns and later on a couple columns could > be added, I'm thinking about creating the table with the known columns in a > classical way and have one additional JSON

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

On Tuesday, 20 June, 2017 07:24, R Smith wrote: > Every lesson is valuable! Just to be clear - there is nothing wrong > with using the CLI. When pointing it to a file that is correctly encoded > the import must work correctly (if not, it's a bug) - It's just > difficult to

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

> Le 20 juin 2017 à 15:56, Simon Slavin a écrit : > > The console you see is pretty-much the one which was in Windows 3.1. It does > not use the modern API written post-unicode, it calls the old > single-character Windows routines which are still in Windows so old

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

> Le 20 juin 2017 à 15:24, R Smith a écrit : > > As an aside - I never understood the reasons for that. I get that Windows has > a less "techy" clientèle than Linux for instance, and that the backwards > compatibility is paramount, and that no console command ever need fall

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

Simon Slavin-3 > To clarify the clarification, you can use the SQLite shell tool just fine as long as you use it to process files, rather than expect characters which are entered through the keyboard or shown on the display to work. So use ".read" or ".output" or ".once", and then use a

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

On 20 Jun 2017, at 2:24pm, R Smith wrote: > Every lesson is valuable! Just to be clear - there is nothing wrong with > using the CLI. When pointing it to a file that is correctly encoded the > import must work correctly (if not, it's a bug) - It's just difficult to >

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

R Smith > >> 2. Do not use the sqlite3.exe CLI if the data use anything more than >> the basic latin alphabet. Instead, use a GUI application (eg. for >> Windows, SQLite Studio, SQLitespeed, etc.) > Every lesson is valuable! Just to be clear - there is nothing wrong with using the CLI. When

Re: [sqlite] Possible issue with 3.19.3

On 6/20/17, Eric Sink wrote: > > Would it be appropriate for me to send the database file to someone for > further investigation? > Yes, please. Send the database directly to me via private email. -- D. Richard Hipp d...@sqlite.org

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

Indeed. Technically-minded Windows users do exist (Hi, Microsoft, I'm right here!), and I have neither the time nor the inclination to learn PowerShell when the Windows terminal is already adequate---with a set of ports of GNU tools, anyway. :) On June 20, 2017 9:24:12 AM EDT, R Smith

[sqlite] Possible issue with 3.19.3

Greetings, Version 3.19.3 is yielding different results than previous releases for a query in the Entity Framework Core test suite. The query looks like this: SELECT [e].[Id], [e].[Discriminator], [e].[Name], [e].[BaseId], [t].[Id], [t].[BaseParentId], [t].[Discriminator], [t].[Name],

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

On 2017/06/20 2:34 PM, Gilles wrote: Lessons I learned: 1. In CSV files, double-check how data are encoded 2. Do not use the sqlite3.exe CLI if the data use anything more than the basic latin alphabet. Instead, use a GUI application (eg. for Windows, SQLite Studio, SQLitespeed, etc.)

Re: [sqlite] JSON1 extension & speed-up by using indices etc.?

On 20 Jun 2017, at 8:46am, Robert M. Münch wrote: > The WHERE parts look like this: > > ... WHERE col-1 <> NULL AND col-2 <> NULL ... AND col-x <> NULL > > ... WHERE col-x LIKE ... My bet is that it’s these clauses which are slowing down execution of your

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

Posted by David Raymond on Jun 19, 2017; 5:22pm > /The Windows command prompt and unicode have always not played well with each other. SQLite itself works perfectly with data on disk or in the database, there are just translation and display problems when going to and from the command prompt.

Re: [sqlite] lsm1 extension

Thanks for the clarification! On Tue, Jun 20, 2017 at 2:41 AM Dan Kennedy wrote: > On 06/20/2017 12:42 PM, Charles Leifer wrote: > > Hi, > > > > I'm not quite sure of the proper way to compile the lsm1 extension (in > the > > lsm-vtab branch). I ended up hand-hacking the

Re: [sqlite] sqlite3_exec statement count including create/drop?

petern wrote: > Regarding sqlite3_trace_v2(db, SQLITE_TRACE_PROFILE,...). Calls to > sqlite3_sql() on the third trace callback parameter (cast to sqlite_stmt*) > do retrieve the correct part of the the original sqlite3_exec input SQL > string except for ill formed SQL. Apparently the

Re: [sqlite] JSON1 extension & speed-up by using indices etc.?

On 20 Jun 2017, at 2:34, Jens Alfke wrote: > My understanding from reading the docs is that SQLite view’s aren’t “built” > at all: their contents have no physical existence in the database, the views > are simply macros that transform the statements that use them. (Correct me if > I’m wrong; I

Re: [sqlite] JSON1 extension & speed-up by using indices etc.?

On 19 Jun 2017, at 17:09, Simon Slavin wrote: >> CREATE VIEW json AS SELECT rec_id, json_extract(json_value,'$.col-1') as >> col1, json_extract(json_value,'$.col-2') as col2, ... , >> json_extract(json_value,'$.col-50') as col50 FROM a > Please supply a same SELECT command that you would use

Re: [sqlite] lsm1 extension

On 06/20/2017 12:42 PM, Charles Leifer wrote: Hi, I'm not quite sure of the proper way to compile the lsm1 extension (in the lsm-vtab branch). I ended up hand-hacking the makefile to replace $(TCCX) and add the appropriate flags for gcc (-fPIC) to get it to build. I'd like to do it the "right