Re: [sqlite] [System.Data.SQLite] Using sqlite3.dll instead of Interop.dll - what's the trade-off?

John Reynolds wrote: > > My question is: what are the trade-offs of not using > SQLite.Interop.dll? > There are various compile-options and extensions baked into the "SQLite.Interop.dll" that are not enabled and/or included by default with "sqlite3.dll". One that is somewhat important, is the

[sqlite] [System.Data.SQLite] Using sqlite3.dll instead of Interop.dll - what's the trade-off?

Hi, (Sorry if this becomes a double post - I first tried posting from Nabble) I've compiled System.Data.SQLite.dll with the "/property:UseSqliteStandard=true" option, so that it will load sqlite3.dll (or it's Linux equivalent) instead of SQLite.Interop.dll. The advantage of this is that you can

Re: [sqlite] WHERE col IN tab

On 9/16/16, Dominique Devienne wrote: > > Is that <> SQL standard? That feature was added to SQLite on 2004-01-15 (http://sqlite.org/src/timeline?c=01874d25). I do not recall why I added it. -- D. Richard Hipp d...@sqlite.org ___ sqlite-users mailing

Re: [sqlite] WHERE col IN tab

On Fri, Sep 16, 2016 at 6:00 PM, J Decker wrote: > but probably what you mean is... > I didn't mean anything. I asked a question about an unusual syntax. > SELECT * FROM t1 join T2 on x=y; > SELECT * FROM t1 join (select y from t2) on x=y > A join works too, but that's beside the point. Logi

Re: [sqlite] how is "pragma threads = 4" working

that is a single sql statement though ; it doesn't spread itself amongst threads, the compile option says 'limits number of threads' so if you had an application (not sqlite shell) that had threads it could have a limit? On Fri, Sep 16, 2016 at 5:13 AM, Adam Devita wrote: > Have you proven that

Re: [sqlite] WHERE col IN tab

IN is for sets, not another table. I'm surprised sqlite didn't thrown an error but probably what you mean is... SELECT * FROM t1 join T2 on x=y; SELECT * FROM t1 join (select y from t2) on x=y select * from table where colName in (1,2,3,4) /// woud return rows where some column has a valu

[sqlite] WHERE col IN tab

Reading https://www.sqlite.org/src/tktview/0eab1ac7591f, (from a very recent thread) I was surprised to read that syntax. So I tried it in SQLite, and it works as shown in the ticket: C:\Users\DDevienne>sqlite3 SQLite version 3.10.2 2016-01-20 15:27:19 sqlite> CREATE TABLE t1(x INTEGER PRIMARY KE

Re: [sqlite] sqlite3 issue report: sqlite3 hung-up on DELETE

Your best work-around is to fix your schema. Do *not* say UNIQUE PRIMARY KEY That is redundant. PRIMARY KEYs are always UNIQUE. Just say PRIMARY KEY and omit the UNIQUE. Of course, SQLite should be able to deal with this redundancy without a dramatic slowdown. That problem will be fixed

Re: [sqlite] sqlite3 issue report: sqlite3 hung-up on DELETE

On 9/16/16, Takasumi Iwamoto wrote: > Hello SQLite devs, > > We've found a hung-up issue in the current sqlite3. > Could you please read the below issue report? Thanks for the bug report. The ticket for this problem is here: https://www.sqlite.org/src/tktview/0eab1ac7591f -- D. Richard Hipp d.

[sqlite] Session documentation: Invalid link for sqlite3_changegroup

The invalid link is in red font. Reference: https://www.sqlite.org/sessionintro.html#extended_functionality Ralf ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] how is "pragma threads = 4" working

Have you proven that the cpu is the bottleneck? Sorting a million rows seems like a lot, but even older single core cpus may be capable of 2 billion ops per second. [I apologize if this has been sorted out already I've got about 2 days of history on the thread] regards, Adam DeVita On Fri, Se

Re: [sqlite] how is "pragma threads = 4" working

Although programmatically easily done, from the SQLite point of view, what if that query, sans LIMIT, were a subquery, and the limit was put out on the outside? Would the inner query execute, use all the threads, then return just one row on the outer? On Fri, Sep 16, 2016 at 7:29 AM, Richard Hipp

[sqlite] sqlite3 issue report: sqlite3 hung-up on DELETE

Hello SQLite devs, We've found a hung-up issue in the current sqlite3. Could you please read the below issue report? === Summary of the issue === For the specified DB, sqlite3 hung-up after invoking the specified DELETE query. Then CPU usage keeps 100% until killing the process. === Affect

Re: [sqlite] how is "pragma threads = 4" working

On 8/14/16, Венцислав Русев wrote: > My computer has 4 cores. I have compile sqlite like this "gcc > -DSQLITE_MAX_WORKER_THREADS=4 -DSQLITE_DEFAULT_WORKER_THREADS=4 shell.c > sqlite3.c -lpthread -ldl -o sqlite3". I made some tests and found that > "pragma threads = 4" doesn't decrease runtime of t

[sqlite] SQLite 3.14.2 autoconf (shell) doesn't build with SQLITE_OMIT_AUTHORIZATION, undefined reference

Hello everyone, I couldn't find this in the existing bug list so I decided to send this email. I downloaded the latest SQLite autoconf version from https://www.sqlite.org/2016/sqlite-autoconf-3140200.tar.gz and tried building it using this compile option, doing CFLAGS="-DSQLITE_OMIT_AUTHORIZATIO

Re: [sqlite] how is "pragma threads = 4" working

On 15 Aug 2016, at 1:02am, Венцислав Русев wrote: > sqlite doesn't use these "auxiliary threads" that sqlite docs talks about and > the runtime of that query is the same with or without "pragma threads = 4". I cannot solve your problem, but this information may help the person who does. Which

[sqlite] how is "pragma threads = 4" working

My computer has 4 cores. I have compile sqlite like this "gcc -DSQLITE_MAX_WORKER_THREADS=4 -DSQLITE_DEFAULT_WORKER_THREADS=4 shell.c sqlite3.c -lpthread -ldl -o sqlite3". I made some tests and found that "pragma threads = 4" doesn't decrease runtime of the query that sorts 1 milion records.

Re: [sqlite] Complicated join

OVER PARTITION BY ... One can dream... - Deon -Original Message- From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of David Raymond Sent: Thursday, September 15, 2016 1:47 PM To: SQLite mailing list Subject: Re: [sqlite] Complicated join Can it be don