| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| |
| |
| |
| |
| |
| | |
* 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.
|
|\ \
| |/
| |
| | |
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.
|
|\ \
| |/
| |
| |
| |
| | |
# Resolved conflicts:
# ext/sqlite3/sqlite3.c
# ext/sqlite3/tests/bug72668.phpt
|
| |
| |
| |
| |
| | |
Not only SQLite3::querySingle(), but also SQLite3::query() and
SQLite3Stmt::execute() were affected.
|
| |
| |
| |
| | |
function)
|
| | |
|
|\ \
| |/ |
|
| |
| |
| |
| |
| | |
Obiously, it isn't sufficient to call sqlite3_clear_bindings() alone, but
also the bound_params of the php_sqlite3_stmt have to be cleared.
|
| | |
|
| |
| |
| |
| | |
Also re bug #71575.
|
|\ \
| |/
| |
| |
| | |
Conflicts:
ext/sqlite3/sqlite3.c
|
| | |
|
|\ \
| |/
| |
| |
| | |
* PHP-5.6:
Happy new year (Update copyright to 2016)
|
| | |
|
| |
| |
| |
| | |
of internal buffer)
|
| |
| |
| |
| | |
rel #70862
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
This was very, very obvious when using a debug build of PHP to build the
manual!
Fixes bug #70571 (Memory leak in sqlite3_do_callback).
|
| | |
|
| | |
|
|\ \
| |/
| |
| |
| | |
Conflicts:
ext/sqlite3/sqlite3.c
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
semantick changes).
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Introduces a ZEND_PARSE_PARAMS_THROW flag for zpp, which forces to
report FAILURE errors using a TypeException instead of a Warning,
like it would happen in strict mode.
Adds a zend_parse_parameters_throw() convenience function, which
invokes zpp with this flag.
Converts all cases I could identify, where we currently have
throwing zpp usage in constructors and replaces them with this API.
Error handling is still replaced to EH_THROW in some cases to handle
other, domain-specific errors in constructors.
|
|\ \
| |/
| |
| |
| |
| |
| |
| | |
* PHP-5.6:
Fix bug #66550 (SQLite prepared statement use-after-free)
Conflicts:
ext/sqlite3/sqlite3.c
|
| |\
| | |
| | |
| | |
| | | |
* PHP-5.5:
Fix bug #66550 (SQLite prepared statement use-after-free)
|
| | |\
| | | |
| | | |
| | | |
| | | | |
* PHP-5.4:
Fix bug #66550 (SQLite prepared statement use-after-free)
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
* pull-request/1091:
Stop trying to call the callback after it has thrown an exception. Also, as an exception has been thrown, there is no need to have a separate error message.
Fix freeing null segfault. Added test for behaviour.
Conflicts:
ext/sqlite3/tests/bug68760.phpt
|
| | | | |
| | | | |
| | | | |
| | | | | |
an exception has been thrown, there is no need to have a separate error message.
|
|/ / / /
| | | |
| | | |
| | | | |
which also comply with the current semantics for such macros
|
| | | |
| | | |
| | | |
| | | | |
zend_object->properties_table[]. As result size of objects without __get/__set/__unset/__isset magic methods is reduced.
|
| | | | |
|
| | | | |
|