Unrelated, but are you sure that you want the albums "id int primary key" and
did not happen to misspell "integer" so that the declaration should be "id
integer primary key". In the former case, id is an integer that just happens
to be unique (ie, "id int primary key" is the same as "id
Hello,
I want to report a bug, I checked https://www.sqlite.org/src/rptview?rn=8
and did not find the same?
Let schema be:
sqlite> .schema
CREATE TABLE albums (id int primary key, title text, score int);
CREATE TABLE rates (album_id references albums(id) on delete cascade,
comment text, score
> Why aren't you measuring the time spent only in the SQLite writing thread?
>
> That would eliminate the overhead from the read-thread(s) and the queue in
> the middle,
> measuring only work by SQLite, instead of including the *waiting* for work
> in the queue.
>
> I wrote a similarly "piped" ETL
On Tue, Oct 2, 2018 at 6:56 PM dmp wrote:
> >> On Sep 25, 2018, at 11:14 AM, dmp
> wrote:
> The timing given takes place at the beginning of the transfer
> process and stops when completed, threads join.
>
Why aren't you measuring the time spent only in the SQLite writing thread?
That would
4 matches
Mail list logo
