Re: [sqlite] rowid changing....

2016-09-17 Thread Clemens Ladisch
mikeegg1 wrote: > The insert statement is a “insert or replace into…” so I don’t have to > deal with insertion errors. However, I expected the rowid to not change > when the row has not changed. The OR REPLACE clause just deletes any old row. If you want to update the old row, use UPDATE. (And t

[sqlite] rowid changing....

2016-09-17 Thread mikeegg1
Happy Saturday. In my DDL I have “integer primary key not null” on my tables. When I do the first insert to these tables the rowid is assigned. The insert statement is a “insert or replace into…” so I don’t have to deal with insertion errors. However, I expected the rowid to not change when the

Re: [sqlite] Complicated join

2016-09-17 Thread David Bicking
EvtNbr cannot be null, and can be 0. (Though I understand if there is any Evtnbr > 0, there can't be an EvtNbr 0, the lowest can be one or higher.) I need to come up with some test data, if only to test the "I'm pretty sure it doesn't work" solution I came up with. One good bit of news is my b

[sqlite] sqldiff -- interpreting the data

2016-09-17 Thread Kumar Suraj
Can anyone please tell me when i use SQLdiff --summary option what does the following row means tablename:0 changes,0 inserts , 288 deletes, 0 unchanged.. ___ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/c

Re: [sqlite] Complicated join

2016-09-17 Thread R Smith
On 2016/09/15 5:53 PM, David Bicking wrote: I have two tables: CREATE TABLE M ( CombineKeyFields, EvtNbr, TransDate, OtherFields, PRIMARY KEY(CombinedKeyFields, EvtNbr, TransDate));CREATE TABLE E ( CombineKeyFields, EvtNbr, TransDate, OtherFields, PRIMARY KEY(CombinedKeyFields, EvtNbr, Trans

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

2016-09-17 Thread Венцислав Русев
On 08/15/2016 12:02 AM, Венцислав Русев 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 runt

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

2016-09-17 Thread Takasumi Iwamoto
Hello Richard Hipp, Thank you for the fast reply. We've confirmed that the work-around works well. We will remove UNIQUE from PRIMARY KEY by default. Thank you again, -- Takasumi Iwamoto On Fri, Sep 16, 2016 at 11:17 PM, Richard Hipp wrote: > Your best work-around is to fix your schema. Do