Change flags to use SQLITE3_OPEN_READ* constants instead of a fake-boolean, add tests on errors

Implement writing to BLOBs in SQLite3

Fix misleading typo in identifiers

fixed bug #74413 wrong reflection on SQLite3::enableExceptions

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 (wheez

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...)

show more ...

Implement FR #74217: deterministic sqlite functions

Update copyright headers to 2017

Update copyright headers to 2017

Update copyright headers to 2017

Revert "Fix #73530: Unsetting result set may reset other result set"

This reverts commit eb570294a289b45d0dd38efc71065d6b0d314c4b.

That commit caused a regression, so it's probably

Revert "Fix #73530: Unsetting result set may reset other result set"

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.

show more ...

Fix #73530: Unsetting result set may reset other result set

Calling sqlite3_reset() when a result set object is freed can cause
undesired and maybe even hard to track interference with o

Fix #73530: Unsetting result set may reset other result set

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.

show more ...

Fix compiler warnings, always cast to zend_long from sqlite3_int64 when converting to a zval

Ignore the return value of sqlite3->busyTimeout() if their "API Armor" is not enabled.

The sqlite3_busy_timeout() function can only ever return SQLITE_OK if the armor is not compiled in, whi

Ignore the return value of sqlite3->busyTimeout() if their "API Armor" is 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

show more ...

Fix #73333: 2147483647 is fetched as string

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 bu

Fix #73333: 2147483647 is fetched as string

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>.

show more ...

Fix typo

Implement #72653: SQLite should allow opening with empty filename

From the [sqlite3_open](https://www.sqlite.org/c3ref/open.html) docs:

| If the filename is an empty string, then a

Implement #72653: SQLite should allow opening with empty filename

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.

show more ...

Further fixes wrt. bug #72668

Not only SQLite3::querySingle(), but also SQLite3::query() and
SQLite3Stmt::execute() were affected.

Fixed bug #72668 (Spurious warning when exception is thrown in user defined function)

Fixed bug #72571 (SQLite3::bindValue, SQLite3::bindParam crash)

Fix #70628: Clearing bindings on an SQLite3 statement doesn't work

Obiously, it isn't sufficient to call sqlite3_clear_bindings() alone, but
also the bound_params of the php_sqlite3_stmt

Fix #70628: Clearing bindings on an SQLite3 statement doesn't work

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.

show more ...

Fixed compilation warnings

Removed "zend_fcall_info.function_table". It was assigned in many places, but is never used.

Fixed bug #68849 bindValue is not using the right data type

Move semicolon into TSRMLS_CACHE_EXTERN/DEFINE

Also re bug #71575.

Removed zend_fcall_info.symbol_table