Req #73068 [Csd]: SQLite3 may fail to DELETE

From: Date: Tue, 13 Sep 2016 14:01:42 +0000
Subject: Req #73068 [Csd]: SQLite3 may fail to DELETE
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-204001@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=73068&edit=1 ID: 73068 Updated by: ab@php.net Reported by: alejosimon at gmail dot com -Summary: Update to SQLite 3.14.2 +Summary: SQLite3 may fail to DELETE Status: Closed Type: Feature/Change Request Package: SQLite related Operating System: Windows 7 x64 PHP Version: Irrelevant Assigned To: ab Block user comment: N Private report: N New Comment: Btw. this is not a bug in PHP, but since we bundle libsqlite, it affects quite some users. Lets keep the title therefore. I've also added a test to this behavior. Thanks. Previous Comments: ------------------------------------------------------------------------ [2016-09-13 14:00:08] ab@php.net I've added libsqlite 3.14.2 to 7.0 dev as well. For the upcoming release, the bundled libsqlite is downgraded to latest known stable 3.8.x. For PHP 7.0.12 we'll see further then, whether to instantly revert libsqlite to 3.8.x or to keep 3.14.2. Thanks. ------------------------------------------------------------------------ [2016-09-13 13:29:10] alejosimon at gmail dot com cmb... ought to be! jeje! ... not forget that most web developers do not compile php, and the Windows users always depend on the compiled versions. thanks! ------------------------------------------------------------------------ [2016-09-13 11:42:10] cmb@php.net I have updated PHP 7.1+ to SQLite 3.14.2, see <http://git.php.net/?p=php-src.git;a=commit;h=07aab07c>. Anatol, should PHP 7.0 be updated as well? ------------------------------------------------------------------------ [2016-09-13 11:25:46] cmb@php.net After further consideration, I don't think this qualifies as bug, because users can compile against a custom libsqlite3. ------------------------------------------------------------------------ [2016-09-13 11:06:51] cmb@php.net I don't think that the second issue is too much of a problem, because the bug report states: > This problem has been in the code since before version 3.3.7 > (2006-08-12), and and hence gone unnoticed for over ten years. > For that reason, it is given a low severity. The first issue, however, appears to be real problem. Anyhow, SQLite 3.14.2 has already been released, so PHP 7.1+ will have to be updated anyway. PHP 5.6 is still on SQLite 3.8.10.2, and as such is not affected by the first issue. It's not yet clear to me what to do with PHP 7.0, which is still on SQLite 3.13.0. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=73068 -- Edit this bug report at https://bugs.php.net/bug.php?id=73068&edit=1

« previous php.bugs (#204001) next »