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 your schema. Do

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: https://www.sqlite.org/src/tktview/0eab1ac7591f -- D. Richard Hipp d.

[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. === Affect

Re: [sqlite] sqlite3 issue in sqlite3VdbeReset

> Why do sqlite3VdbeReset() always produces problem; What problem? Why 'always' if only you complain and it works in other's applications? > Could you please provide any help in this issue. Run valgrind on your application and see where memory is getting corrupted or double-freed. Pavel On We

[sqlite] sqlite3 issue in sqlite3VdbeReset

Hi, Why do sqlite3VdbeReset() always produces problem; Please check the following calling stack trace of one of our module which crashes because of sqlite3 library. #4056 0x4805eed0 in sqlite3VdbeMemRelease () #4057 0x4805eed0 in sqlite3VdbeMemRelease () #4058 0x4805eed0 in sqlite3VdbeMemRelease

[sqlite] SQLite3 Issue - Solved

Hi there, Thanks a lot Richard for your quick reply. I found the source of the error. gdb was displaying it in sqlite3_step but it was actually two lines before. Regards, David - Get easy, one-click access to your favorites. Make Yahoo! your

Re: [sqlite] SQLite3 Issue

David Gelt <[EMAIL PROTECTED]> wrote: > > db_reset_stmt(dbo, stmt); > * SEGMENTATION FAULT AT THE > NEXT LINE * > return_code = db_fetch_first(dbo, stmt); /* initial call to retrieve sqlite3_col

[sqlite] SQLite3 Issue

Hi there, I have started using recently SQLite which is pretty great for what I need, (i.e. a scientific application). After going through PostgreSQL, CDB, Tiny CDB and Berkeley DB it feels like coming home when I am looking at the size, speed, number of features and license. :) An