| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The fix for feature request #53466 did not properly handle resetting of
the corresponding statement; the problem with this is that the
statement does not know about its result sets. But even if we could
fix this, the `complete` handling still appears to be brittle, since
the `sqlite3_column_type()`docs[1] state:
| If the SQL statement does not currently point to a valid row, or if
| the column index is out of range, the result is undefined.
Fortunately, we can use `sqlite3_data_count()` instead, since[2]:
| If prepared statement P does not have results ready to return (via
| calls to the sqlite3_column() family of interfaces) then
| sqlite3_data_count(P) returns 0.
Thus, we guard `SQLite3::columnType()` with `sqlite3_data_count()`, and
completely drop updating the `php_sqlite3_result_object.complete`
field, but keep it for ABI BC purposes.
[1] <https://www.sqlite.org/c3ref/column_blob.html>
[2] <https://www.sqlite.org/c3ref/data_count.html>
|
|\
| |
| |
| |
| | |
* PHP-7.2:
Fix bug #77967 - Bypassing open_basedir restrictions via file uris
|
| |\
| | |
| | |
| | |
| | | |
* PHP-7.1:
Fix bug #77967 - Bypassing open_basedir restrictions via file uris
|
| | | |
|
| | |
| | |
| | |
| | | |
against potential security flaws
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.2:
SQLite3: add DEFENSIVE config for SQLite >= 3.26.0 as a mitigation strategy against potential security flaws
|
| | |
| | |
| | |
| | | |
against potential security flaws
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.2:
Fix #77051: Issue with re-binding on SQLite3
|
| | |
| | |
| | |
| | | |
We have to call `sqlite3_reset()` before re-binding the parameters.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.2:
Fix #76665: SQLite3Stmt::bindValue() with SQLITE3_FLOAT doesn't juggle
|
| |\ \
| | |/
| | |
| | |
| | | |
* 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.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The $Id$ keywords were used in Subversion where they can be substituted
with filename, last revision number change, last changed date, and last
user who changed it.
In Git this functionality is different and can be done with Git attribute
ident. These need to be defined manually for each file in the
.gitattributes file and are afterwards replaced with 40-character
hexadecimal blob object name which is based only on the particular file
contents.
This patch simplifies handling of $Id$ keywords by removing them since
they are not used anymore.
|
| | |
| | |
| | |
| | | |
destroy new created object (This is safer and produces less code)
|
| | |
| | |
| | |
| | |
| | | |
The rest of the core extensions don't display the extension versions in
the phpinfo output since they in most cases match the PHP release version.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
where we sure about string persistence.
|
| | |
| | |
| | |
| | | |
__construct, __destruct, __wakeup does not have return types defined.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Using ecalloc() to create objects is expensive, because the
dynamic-size memset() is unreasonably slow. Make sure we only
zero the main object structure with known size, as the properties
are intialized separately anyway.
Technically we do not need to zero the embedded zend_object
structure either, but as long as the memset argument is constant,
a couple more bytes don't really matter.
|
|/ / |
|
|\ \
| |/
| |
| |
| | |
* 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...)
|
|\ \ \
| |/ / |
|
| | | |
|
| | | |
|
| | | |
|