[sqlite] Any way to disable transactional behavior?

I have a program that writes hundreds of thousands of statements that are logically unrelated, i.e. each is "transactional". The problem is if I don't do a BEGIN TRANSACTION and do my inserts, it takes absolutely forever for my program to finish (we're talking hours). If instead I do it in a

Re: [sqlite] CREATE TABLE/ALTER TABLE Slow Down When Table Count Grow

How many system objects do you have that this is a problem? > -Original Message- > From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] > On Behalf Of sanhua.zh > Sent: Sunday, 9 October, 2016 21:53 > To: sqlite-users > Subject: [sqlite] CREATE TABLE/ALTER TABLE Slow

[sqlite] CREATE TABLE/ALTER TABLE Slow Down When Table Count Grow

I foundCREATE TABLE/ALTER TABLE Slow Down When Table Count Grow. Since those SQLs modify the schema, SQLite use theOP_ParseSchema to update them, which cause the search of sqlite_master. (SELECT name, rootpage, sql FROM '%q'.%s WHERE %s ORDER BY rowid) As we all know, sqlite_master has no index

Re: [sqlite] Parallel access to read only in memory database

Jens Alfke wrote: On Oct 9, 2016, at 8:15 AM, Howard Chu wrote: Use SQLightning, it's designed specifically for write once read many workloads. "SQLite3 ported to use LMDB instead of its original Btree code” — sounds great, and the performance figures quoted in the readme

Re: [sqlite] Backward compatibility of indexes with "WHERE function()"

> On Oct 8, 2016, at 1:39 PM, Richard Hipp <d...@sqlite.org> wrote: > > See http://sqlite.org/graphs/size-20161009.jpg > <http://sqlite.org/graphs/size-20161009.jpg> for a graph of > compiled-binary size using gcc 4.8.4 and -Os on x64 Linux. Less than

Re: [sqlite] Parallel access to read only in memory database

> On Oct 9, 2016, at 8:15 AM, Howard Chu wrote: > > Use SQLightning, it's designed specifically for write once read many > workloads. "SQLite3 ported to use LMDB instead of its original Btree code” — sounds great, and the performance figures quoted in the readme are

Re: [sqlite] Parallel access to read only in memory database

Hello ! But SQLightning is a dead project, isn't it ? version 3.7.17 hyc committed on 12 Sep 2013 Cheers ! On 09/10/16 12:15, Howard Chu

Re: [sqlite] Parallel access to read only in memory database

Daniel Meyer wrote: We are interested in using sqlite as a read only, in memory, parallel access database. We have database files that are on the order of 100GB that we are loading into memory. We have found great performance when reading from a single thread. We need to scale up to have many

Re: [sqlite] SQL parsing logic for triggers

On Sun, Oct 9, 2016 at 12:14 PM, Richard Hipp wrote: > On 10/9/16, gwenn wrote: >> Hello, >> I am just looking for information (I am not asking for any change): >> It is for (auto) completion hints. >> >> 1) it seems not possible to insert default values in

[sqlite] 回复： The Performance Between [Drop Table] And [Rename Table] ?

Now I found the possible reason why [Rename Table] become slow. While the one table renamed, the schema need to be updated. But SQLite use the ['SELECT name, rootpage, sql FROM 'main'.sqlite_master WHERE tbl_name=’tablename' ORDER BY rowid”] to update the schema. Isn’t it too ugly ? Why we

Re: [sqlite] SQL parsing logic for triggers

On 10/9/16, gwenn wrote: > Hello, > I am just looking for information (I am not asking for any change): > It is for (auto) completion hints. > > 1) it seems not possible to insert default values in trigger command: > > // INSERT > trigger_cmd(A) ::= insert_cmd(R) INTO

[sqlite] The Performance Between [Drop Table] And [Rename Table] ?

I found that [Rename Table](using ‘ALTER TABLE RENAME TO') is much slower than [Drop Table]. The cost of [Rename Table] may be twice, even if the table is empty(which means it has no index, no trigger, no view and no column). As I known, both [Drop Table] and [Rename Table] just modify the

Re: [sqlite] SQL parsing logic for triggers

Sorry, I've just found the answer to the first question here: http://www.sqlite.org/lang_insert.html Regards. On Sun, Oct 9, 2016 at 10:34 AM, gwenn wrote: > Hello, > I am just looking for information (I am not asking for any change): > It is for (auto) completion hints. >

Re: [sqlite] Backward compatibility of indexes with "WHERE function()"

On 9 Oct 2016, at 9:32am, R Smith wrote: > most everybody else in the World (including North America) seems to more > easily understand "Indexes" as the plural That's why I used it here. Formal English requires that I write 'indices' and that's what I used when I started

[sqlite] SQL parsing logic for triggers

Hello, I am just looking for information (I am not asking for any change): It is for (auto) completion hints. 1) it seems not possible to insert default values in trigger command: // INSERT trigger_cmd(A) ::= insert_cmd(R) INTO trnm(X) idlist_opt(F) select(S). versus //

Re: [sqlite] Backward compatibility of indexes with "WHERE function()"

On 2016/10/08 9:41 PM, Jens Alfke wrote: —Jens * is it ‘indexes’ or ‘indices’, in computer science? It is both, and I pedantically prefer "Indices", but there's been some debate and you can find on-line literature in support of all views. The correct original "English" is of course