Re: [sqlite] EXT :Re: Concurrent readonly access to a large database.

Hi Bo, > boun...@sqlite.org] On Behalf Of Bo Peng > > I wonder if it would be better on just having the data organized > > before loading it, so that the records in each of the 5000 tables > > would be contiguously stored. Of course, that also depends on how much > > new data will be added to the

Re: [sqlite] triggers : NEW keyword with multiple tables

On 10/25/2011 10:59 AM, Sébastien Escudier wrote: Hello, I used to do something like this on older sqlite versions : (this does not really makes sense here, but this is a simplified) CREATE VIEW my_view AS SELECT table1.type, table2.type FROM table1 INNER JOIN table2 ON table1.id = table2.id;

Re: [sqlite] Help with sqlite3OsRead - porting to a new OS

Also, if this is debugger output (as it appears), it could be that an optimizer is confusing the parameters. I see that all the time on GCC i386 when I set a breakpoint at the start of a function. --David David Garfield writes: > Sounds like it could be a difference in calling convention...

Re: [sqlite] Help with sqlite3OsRead - porting to a new OS

Sounds like it could be a difference in calling convention... Check compile options and function declaration modifiers. --David Stuart Thomson writes: > Hi, > > I'm in the middle of porting sqlite3 to a new Operating System and have come > across a problem with the sqlite3OsRead function in

Re: [sqlite] triggers : NEW keyword with multiple tables

On Oct 25, 2011, at 10:59 AM, Sébastien Escudier wrote: > CREATE TRIGGER my_trigger INSTEAD OF INSERT ON my_view > BEGIN > INSERT INTO table1(type) VALUES(NEW.table1.type); > INSERT INTO table2(type) VALUES(NEW.table2.type); > END; > > ... > > Why this syntax does not work anymore ? You

[sqlite] triggers : NEW keyword with multiple tables

Hello, I used to do something like this on older sqlite versions : (this does not really makes sense here, but this is a simplified) CREATE VIEW my_view AS SELECT table1.type, table2.type FROM table1 INNER JOIN table2 ON table1.id = table2.id; CREATE TRIGGER my_trigger INSTEAD OF INSERT ON

Re: [sqlite] EXT :Re: Concurrent readonly access to a large database.

2011/10/25 Bo Peng : > Tables are added in batch and then kept unchanged. I mean, a database > might have 1000 new tables one day, and 2000 later. All operations are > on single tables. > > Each table is for one 'sample'. All tables have one column for 'item > id', and optional

Re: [sqlite] EXT :Re: Concurrent readonly access to a large database.

> Doing vacuum on a 288 Gb database is probably going to take some time. I submitted the command yesterday night and nothing seems to be happening after 8 hours (sqlite3 is running and there is disk activity, but I do not see a .journal file). > I wonder if it would be better on just having the

[sqlite] [patch] Re: Potential bug: "insert into X select * from Y" ignores the "ON CONFLICT REPLACE" conflict-clause

David wrote: > Simon L wrote 2011-10-25 06:20: >> To reproduce this problem, enter the following 5 SQL statements at the >> SQLite command line. >> >> create table X(id INTEGER primary key ON CONFLICT REPLACE); >> create table Y(id INTEGER primary key ON CONFLICT REPLACE); >> insert into X values

Re: [sqlite] Virtual Tables and tcl / apsw

On 10/25/2011 04:28 PM, Alexey Pechnikov wrote: 2011/10/25 Dan Kennedy: Not possible. The Tcl interface has no bindings for either the virtual table or VFS interfaces. But why? Is there any technical/ideological problems? None that are insurmountable, I would think.

Re: [sqlite] Virtual Tables and tcl / apsw

2011/10/25 Dan Kennedy : > Not possible. The Tcl interface has no bindings for either the > virtual table or VFS interfaces. But why? Is there any technical/ideological problems? -- Best regards, Alexey Pechnikov. http://pechnikov.tel/

Re: [sqlite] Problem with FTS4 - Floating point error.

On 25-Oct-2011, at 2:53 PM, Dan Kennedy wrote: > This was fixed and then I forgot to follow up here. I should have. > Sorry about that. It's fixed here: > > http://www.sqlite.org/src/ci/3126754c72?sbs=0 > > Either updating to the latest trunk or just applying the linked > patch to fts3.c

Re: [sqlite] Potential bug: "insert into X select * from Y" ignores the "ON CONFLICT REPLACE" conflict-clause

Simon L wrote 2011-10-25 06:20: To reproduce this problem, enter the following 5 SQL statements at the SQLite command line. create table X(id INTEGER primary key ON CONFLICT REPLACE); create table Y(id INTEGER primary key ON CONFLICT REPLACE); insert into X values (1); insert into Y select *

[sqlite] Help with sqlite3OsRead - porting to a new OS

Hi, I'm in the middle of porting sqlite3 to a new Operating System and have come across a problem with the sqlite3OsRead function in the sqlite3PagerReadFileheader function body. Before the sqlite3OsRead function is called, the parameters are correctly populated for example: pPager->fd

Re: [sqlite] Virtual Tables and tcl / apsw

On 10/25/2011 02:31 PM, sqlite-us...@h-rd.org wrote: Hi, I have some questions on virtual tables and tcl compared to perl and python/apsw. As I understand you can build your own virtual table implementation with apsw (and also with perl). Is this also possible with tclsqlite? Any pointers

[sqlite] Virtual Tables and tcl / apsw

Hi, I have some questions on virtual tables and tcl compared to perl and python/apsw. As I understand you can build your own virtual table implementation with apsw (and also with perl). Is this also possible with tclsqlite? Any pointers greatly appreciated, I could not find it in the

Re: [sqlite] Problem with FTS4 - Floating point error.

On 10/25/2011 12:49 PM, Mohd Radzi Ibrahim wrote: On 18-Oct-2011, at 6:52 PM, Dan Kennedy wrote: On 10/18/2011 05:02 PM, Mohd Radzi Ibrahim wrote: Hi, This is my table schema: CREATE VIRTUAL TABLE LocationFTS using FTS4 ( name text, address text, email text,