delta/php-git.git/ext/sqlite3/tests, branch php-7.1.1 git.php.net: repository/php-src.git Merge branch 'PHP-7.0' into PHP-7.1 2016-11-16T13:47:22+00:00 Dmitry Stogov dmitry@zend.com 2016-11-16T13:47:22+00:00 1f3a5b45019d318179113b79d2b92fcb367c1ab7 * PHP-7.0: Fixed ZTS build 
* PHP-7.0:
  Fixed ZTS build
Merge branch 'PHP-7.0' into PHP-7.1 2016-11-16T11:02:29+00:00 Christoph M. Becker cmbecker69@gmx.de 2016-11-16T11:01:55+00:00 c5abb873221e549f02ba0a7bbcc0a47e036e681e 






Merge branch 'PHP-5.6' into PHP-7.0
2016-11-16T11:00:39+00:00

Christoph M. Becker
cmbecker69@gmx.de

2016-11-16T10:55:57+00:00

936cafe33e3115ea04df7902d6eac8d9f63f7fb6












Fix #73530: Unsetting result set may reset other result set
2016-11-16T10:49:04+00:00

Christoph M. Becker
cmbecker69@gmx.de

2016-11-16T10:49:04+00:00

eb570294a289b45d0dd38efc71065d6b0d314c4b

Calling sqlite3_reset() when a result set object is freed can cause
undesired and maybe even hard to track interference with other result
sets. Furthermore, there is no need to call sqlite3_reset(), because
that is implicitly called on SQLite3Stmt::execute(), and users are
encouraged to explicitly call either SQLite3Result::finalize() or
SQLite3Stmt::reset() anyway.





Calling sqlite3_reset() when a result set object is freed can cause
undesired and maybe even hard to track interference with other result
sets. Furthermore, there is no need to call sqlite3_reset(), because
that is implicitly called on SQLite3Stmt::execute(), and users are
encouraged to explicitly call either SQLite3Result::finalize() or
SQLite3Stmt::reset() anyway.







Merge branch 'PHP-7.0' into PHP-7.1
2016-10-17T22:01:32+00:00

Christoph M. Becker
cmbecker69@gmx.de

2016-10-17T22:00:37+00:00

32123167d19841c1e1bb6ca746a9c998d00df31d












Merge branch 'PHP-5.6' into PHP-7.0
2016-10-17T21:38:28+00:00

Christoph M. Becker
cmbecker69@gmx.de

2016-10-17T21:37:00+00:00

0b596f81b8f151969898c040db41bbb7c64c275a

We also use ZEND_LONG_(MAX|MIN) now instead of LONG_(MAX|MIN).





We also use ZEND_LONG_(MAX|MIN) now instead of LONG_(MAX|MIN).







Fix #73333: 2147483647 is fetched as string
2016-10-17T21:34:41+00:00

Christoph M. Becker
cmbecker69@gmx.de

2016-10-17T14:58:49+00:00

86e603a664afdc3a12ead0eaca5d37fa8a379381

We return all integers that can be represented as such by PHP as
integers, and only those that exceed the possible range as strings.
On builds which represent integers with 64 bits, the range check is
unnecessary and might cause code checkers to complain, so we skip this
special casing via the preprocessor according to
<http://git.php.net/?p=php-src.git;a=commit;h=99d087e5>.





We return all integers that can be represented as such by PHP as
integers, and only those that exceed the possible range as strings.
On builds which represent integers with 64 bits, the range check is
unnecessary and might cause code checkers to complain, so we skip this
special casing via the preprocessor according to
<http://git.php.net/?p=php-src.git;a=commit;h=99d087e5>.







Merge branch 'PHP-7.0' into PHP-7.1
2016-09-13T13:30:35+00:00

Anatol Belski
ab@php.net

2016-09-13T13:30:35+00:00

86d6f29e8f763cfa25e966c67699e225e52586f6

* PHP-7.0:
  add test for bug #73068





* PHP-7.0:
  add test for bug #73068







Merge branch 'PHP-5.6' into PHP-7.0
2016-09-13T13:29:46+00:00

Anatol Belski
ab@php.net

2016-09-13T13:29:46+00:00

5163925796790e66edd6abbf1a437e1e50deeb8b

* PHP-5.6:
  add test for bug #73068





* PHP-5.6:
  add test for bug #73068







add test for bug #73068
2016-09-13T13:28:28+00:00

Anatol Belski
ab@php.net

2016-09-13T13:28:28+00:00

248f8c3a91ce28d2d7b1096e6b381ba9029896db