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

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

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

Your best work-around is to fix your schema. Do *not* say UNIQUE PRIMARY KEY That is redundant. PRIMARY KEYs are always UNIQUE. Just say PRIMARY KEY and omit the UNIQUE. Of course, SQLite should be able to deal with this redundancy without a dramatic slowdown. That problem will be fixed

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

On 9/16/16, Takasumi Iwamoto wrote: > Hello SQLite devs, > > We've found a hung-up issue in the current sqlite3. > Could you please read the below issue report? Thanks for the bug report. The ticket for this problem is here:

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

Hello SQLite devs, We've found a hung-up issue in the current sqlite3. Could you please read the below issue report? === Summary of the issue === For the specified DB, sqlite3 hung-up after invoking the specified DELETE query. Then CPU usage keeps 100% until killing the process. ===