Re: [sqlite] Some queries with ORDER BY and LIMIT lock DB

On 9/7/18, Firecore wrote: > > It looks like the latest public version of sqlite v3.24.0 has an issue with > processing queries with ORDER BY and LIMIT against some datasets. Thanks for the bug report. The trouble ticket can be found at

Re: [sqlite] sql UPDATE schema

On 8 Sep 2018, at 1:48am, Amno Jeeuw wrote: > the application generates the following schema represented on this message > box: > db_snapshot3.png > This command is incorrect. It should end in WHERE id

Re: [sqlite] sql UPDATE schema

Your picture of the SQL statement is missing an operator -- your expression after WHERE is malformed. --- The fact that there's a Highway to Hell but only a Stairway to Heaven says a lot about anticipated traffic volume. >-Original Message- >From: sqlite-users [mailto:sqlite-users-

Re: [sqlite] Can you use ORDER BY clause in aggregate functions?

>Can you use ORDER BY clause in aggregate functions? It seems that you >cannot; it is only available for window functions. >However, sometimes is useful using ORDER BY with aggregate functions >that aren't window functions, such as GROUP_CONCAT function. >Therefore is the suggestion to add it if

[sqlite] sql UPDATE schema

I have a database table named company that looks like this: db_snapshot2.png When the application is asked to change the value of ArbolOne to ArbolOn db_snapshot1.png

Re: [sqlite] Some queries with ORDER BY and LIMIT lock DB

On 07 Sep 2018, at 20:20, Richard Hipp wrote: > On 9/7/18, Firecore wrote: >> >> It's easily reproduced with the sqlite3 client and db file available here >> (https://www.dropbox.com/s/l1xofadq7vi5vjj/lock_issue.db?dl=0): > > I cannot reproduce it. It always runs instantly for me. I also ran

Re: [sqlite] Some queries with ORDER BY and LIMIT lock DB

On 9/7/18, Stephen Chrzanowski wrote: > I can reproduce this issue with the SQLite3.exe under Win7. It depends on compile-time options. I have a repro case now. -- D. Richard Hipp d...@sqlite.org ___ sqlite-users mailing list

Re: [sqlite] [EXTERNAL] Can you use ORDER BY clause in aggregate functions?

I am not sure what you are trying to achieve. Can you give an example? -Ursprüngliche Nachricht- Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im Auftrag von sql...@zzo38computer.org Gesendet: Freitag, 07. September 2018 21:30 An:

Re: [sqlite] Some queries with ORDER BY and LIMIT lock DB

I can reproduce this issue with the SQLite3.exe under Win7. The first sqlite3 was pulled from a sqlite3.exe I have somewhere in my path, I then extracted the 3.24.0 version to the Ramdrive and executed from there. On the first run, r:\sqlite3.exe did not exist. R:\>sqlite3 lock_issue.db SQLite

[sqlite] Can you use ORDER BY clause in aggregate functions?

Can you use ORDER BY clause in aggregate functions? It seems that you cannot; it is only available for window functions. However, sometimes is useful using ORDER BY with aggregate functions that aren't window functions, such as GROUP_CONCAT function. Therefore is the suggestion to add it if it

Re: [sqlite] Some queries with ORDER BY and LIMIT lock DB

On 9/7/18, Firecore wrote: > > It's easily reproduced with the sqlite3 client and db file available here > (https://www.dropbox.com/s/l1xofadq7vi5vjj/lock_issue.db?dl=0): I cannot reproduce it. It always runs instantly for me. I also ran it under valgrind with no issues reported. -- D.

Re: [sqlite] Some queries with ORDER BY and LIMIT lock DB

Other notes: Order by ASC works ok. Removing ORDER BY works ok. Removing limit works ok. *Limit of more than 1 works ok. But order by DESC, limit 1 sits forever As to work around, leave out the limit and just fetch one row, or do "...limit 2" and just use the first. -Original

[sqlite] Some queries with ORDER BY and LIMIT lock DB

Hi all - It looks like the latest public version of sqlite v3.24.0 has an issue with processing queries with ORDER BY and LIMIT against some datasets. In essence, sqlite3_step returns SQLITE_LOCKED for some of these statments even if there are no other active connections. We were able to

[sqlite] Bug Report: "Is Null" where term propagated to a virtual table causes wrong query results

Hello, I have found an obscure bug in the virtual table processing. The schema looks like this: CREATE TABLE t1 (id int, value text); INSERT INTO t1 VALUES(1,'try'); CREATE TABLE t2 (ctx int, id int, value text); INSERT INTO t2 VALUES(1,1,'good'); INSERT INTO t2 VALUES(2,2,'evil'); The

Re: [sqlite] SQLiteJava

[Bcc'ing the openjfx-dev list] I see no indication that there is anything relating to JavaFX in your question, so there seems to be no need to include the openjfx-dev list. -- Kevin On 9/6/2018 3:21 PM, AmnoJeeuw wrote: I have a database table named company that looks like this: snapshot2

[sqlite] Sqlite Doc Error ?

https://www.sqlite.org/limits.html *Maximum Length Of An SQL Statement* The maximum number of bytes in the text of an SQL statement is limited to SQLITE_MAX_SQL_LENGTH which defaults to 100. You can redefine this limit to be as large as the smaller of SQLITE_MAX_LENGTH and 1073741824. but