| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| | |
* PHP-7.1:
Fix bug #77967 - Bypassing open_basedir restrictions via file uris
|
| | |
|
| |
| |
| |
| | |
against potential security flaws
|
| |
| |
| |
| | |
against potential security flaws
|
| |
| |
| |
| | |
We have to call `sqlite3_reset()` before re-binding the parameters.
|
|\ \
| |/
| |
| |
| | |
* PHP-7.1:
Fix #76665: SQLite3Stmt::bindValue() with SQLITE3_FLOAT doesn't juggle
|
| |
| |
| |
| |
| | |
We need to ensure that a zval IS_DOUBLE before we access it as such.
In this case we apply common type juggling to do so.
|
| | |
|
| | |
|
|\ \
| |/
| |
| |
| | |
* PHP-7.1:
fix build with old system libsqlite (sqlite3_errstr may be missing)
|
| |\
| | |
| | |
| | |
| | | |
* PHP-7.0:
fix build with old system libsqlite (sqlite3_errstr may be missing)
|
| | | |
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.1:
Fixed bug #74883 SQLite3::__construct() produces "out of memory" exception with invalid flags
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.0:
Fixed bug #74883 SQLite3::__construct() produces "out of memory" exception with invalid flags
|
| | |
| | |
| | |
| | | |
with invalid flags
|
| | |
| | |
| | |
| | |
| | | |
Mostly the callback name is only used to report an error. Try to
avoid calculating it if no error occurred.
|
| | |
| | |
| | |
| | | |
add tests on errors
|
| | | |
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.1:
Fix misleading typo in identifiers
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.0:
Fix misleading typo in identifiers
|
| | | |
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.1:
fixed bug #74413 wrong reflection on SQLite3::enableExceptions
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.0:
fixed bug #74413 wrong reflection on SQLite3::enableExceptions
|
| | | |
|
| | | |
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.1:
Fix buid with system libsqlite, see bug #74217
|
| | |
| | |
| | |
| | |
| | |
| | | |
SQLITE_DETERMINISTIC only exists in recent version
e.g. missing on 3.7 which is the default on RHEL/CentOS-7
and probably others (wheezy have 3.7, jessie 3.8...)
|
|\ \ \
| |/ / |
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.1:
Revert "Fix #73530: Unsetting result set may reset other result set"
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.0:
Revert "Fix #73530: Unsetting result set may reset other result set"
|
| | |\
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
* PHP-5.6:
Revert "Fix #73530: Unsetting result set may reset other result set"
# Conflicts:
# ext/sqlite3/sqlite3.c
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This reverts commit eb570294a289b45d0dd38efc71065d6b0d314c4b.
That commit caused a regression, so it's probably best to revert it, and
to tackle the issue for the next minor release.
|
|\ \ \ \
| |/ / / |
|
| |\ \ \
| | |/ / |
|
| | |\ \
| | | |/ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| | | |
| | | |
| | | |
| | | | |
converting to a zval
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
not enabled.
The sqlite3_busy_timeout() function can only ever return SQLITE_OK if the armor is not compiled in, which means we can skip this error check
|
|\ \ \ \
| |/ / / |
|
| |\ \ \
| | |/ / |
|
| | |\ \
| | | |/
| | | |
| | | | |
We also use ZEND_LONG_(MAX|MIN) now instead of LONG_(MAX|MIN).
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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>.
|
|/ / / |
|
|\ \ \
| |/ / |
|
| |\ \
| | |/
| | |
| | |
| | | |
# Resolved conflicts:
# ext/sqlite3/sqlite3.c
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
From the [sqlite3_open](https://www.sqlite.org/c3ref/open.html) docs:
| If the filename is an empty string, then a private, temporary on-disk
| database will be created. This private database will be automatically
| deleted as soon as the database connection is closed.
We make that facility available to userland.
While we're at it, we also do some minor optimizations, remove the
unnecessary check for NUL characters in filename, which is already catered
to by ZPP(p), and add a missing `return` in case db_obj isn't initialized.
|
|\ \ \
| |/ / |
|