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,
On Fri, Sep 16, 2016 at 11:17 PM, Richard Hipp <d...@sqlite.org> wrote:
> 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 in the 3.15.0
> release. We will also add test cases to try to prevent a recurrence
> of this or similar problems.
> But in the meantime, just remove the UNIQUE from all your PRIMARY KEYs
> and your performance issues should go away. For all versions of
> On 9/16/16, Richard Hipp <d...@sqlite.org> wrote:
>> On 9/16/16, Takasumi Iwamoto <takasumi_iwam...@digion.com> 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:
>> D. Richard Hipp
> D. Richard Hipp
> sqlite-users mailing list
sqlite-users mailing list