On Tue, Jul 14, 2015 at 11:41 AM, Yuriy M. Kaminskiy <[email protected]> wrote: > Package: libsqlite3-dev > Version: 3.8.7.1-1+deb8u1 > Followup-For: Bug #736463 > > (was sent to unrelated bug, resenting, sorry) > 1) I was able to reproduce this bug in jessie's 3.8.7.1 (gdb and valgrind > report attached); > 2) I was *NOT* able to reproduce it in (self-backported) sid's 3.8.10.2-1 > (and running under valgrind does not show any problem). > [fwiw, test.db created by sid {totally expectdly} kills jessie's sqlite3 on > attempt to open it]. > However, I have not found respective entry in changelogs (or upstream > commit), so this could be false positive. I can only repeat that the quick solution to remove UNIQUE, the PRIMARY KEY itself guarantee that the specified column will be unique.
Cheers, Laszlo/GCS -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
