Req #73068 [Ver->Csd]: Update to SQLite 3.14.2
| From: | ab@php.net | Date: | Tue, 13 Sep 2016 14:00:08 +0000 |
| Subject: | Req #73068 [Ver->Csd]: Update to SQLite 3.14.2 | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-204000@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
-Status: Verified
+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:
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.
Previous Comments:
------------------------------------------------------------------------
[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.
------------------------------------------------------------------------
[2016-09-12 23:38:24] alejosimon at gmail dot com
Description:
------------
In the last realease of sqlite anunce 2 important bug fixed:
https://sqlite.org/src/info/ef360601
https://sqlite.org/src/info/199df4168c
Especially the first one, I think that should be updated immediately for being a common use query as
DELETE.
Thank you, sorry for my english.
Test script:
---------------
<?php
$db = new \PDO( 'sqlite::memory:' ) ;
$db->exec( "
CREATE TABLE IF NOT EXISTS t1(a INT UNIQUE, b INT);
INSERT OR REPLACE INTO t1(a,b) VALUES('1','2');
SELECT * FROM t1 WHERE a='1' AND b='2';
DELETE FROM t1 WHERE a='1' AND b='2';
" );
print_r( $db->query( "SELECT * FROM t1;" )->fetchAll() );
?>
Expected result:
----------------
Array
(
)
Actual result:
--------------
Array
(
[0] => Array
(
[a] => 1
[0] => 1
[b] => 2
[1] => 2
)
)
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=73068&edit=1