| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Related to GH-6701
|
|
|
|
| |
Closes GH-6691
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This deprecates passing null to non-nullable scale arguments of
internal functions, with the eventual goal of making the behavior
consistent with userland functions, where null is never accepted
for non-nullable arguments.
This change is expected to cause quite a lot of fallout. In most
cases, calling code should be adjusted to avoid passing null. In
some cases, PHP should be adjusted to make some function arguments
nullable. I have already fixed a number of functions before landing
this, but feel free to file a bug if you encounter a function that
doesn't accept null, but probably should. (The rule of thumb for
this to be applicable is that the function must have special behavior
for 0 or "", which is distinct from the natural behavior of the
parameter.)
RFC: https://wiki.php.net/rfc/deprecate_null_to_scalar_internal_arg
Closes GH-6475.
|
|
|
|
|
|
|
| |
We're starting to see a mix between uses of zend_bool and bool.
Replace all usages with the standard bool type everywhere.
Of course, zend_bool is retained as an alias.
|
|
|
|
|
|
| |
We must not release the strings until we are done with them.
Closes GH-6579.
|
|\
| |
| |
| |
| | |
* PHP-7.4:
Fix format specifier
|
| |\
| | |
| | |
| | |
| | | |
* PHP-7.3:
Fix format specifier
|
| | |
| | |
| | |
| | | |
In this function, `i` is of type `size_t`.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.4:
Fix #44618: Fetching may rely on uninitialized data
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.3:
Fix #44618: Fetching may rely on uninitialized data
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Unless `SQLGetData()` returns `SQL_SUCCESS` or `SQL_SUCCESS_WITH_INFO`,
the `StrLen_or_IndPtr` output argument is not guaranteed to be properly
set. Thus we handle retrieval failure other than `SQL_ERROR` by
yielding `false` for those column values and raising a warning.
Closes GH-6281.
|
| | |
| | |
| | |
| | | |
Closes GH-6303.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
These are typical boolean parameters, so we shouldn't advertize them as
integers. For the `$reverse` parameter that even fixes expectations,
because the `reverse` member is a bitfield of 1 bit, so assigning any
even integer would not set it.
Closes GH-6328.
|
| | |
| | |
| | |
| | | |
Closes GH-6243.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.4:
Fix #46050: odbc_next_result corrupts prepared resource
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.3:
Fix #46050: odbc_next_result corrupts prepared resource
|
| | |
| | |
| | |
| | | |
When resetting the result's values, we also have to reset its numcols.
|
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts commit a6ecafece90909d74a578e09f626e875d3035eab.
Closes GH-6242.
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.4:
Fix #80152: odbc_execute() moves internal pointer of $params
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.3:
Fix #80152: odbc_execute() moves internal pointer of $params
|
| | |
| | |
| | |
| | |
| | |
| | | |
As least intrusive fix, we separate the passed array argument.
Closes GH-6219.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
`odbc_connect()` should not reuse persistent connections, since that
prohibits multiple concurrent connections, which are occasionally
desireable. We fix that by no longer looking for already cached
connections when `odbc_connect()` is called, and instead creating a new
connection instead.
Closes GH-6223.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.4:
Fix #80150: Failure to fetch error message
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.3:
Fix #80150: Failure to fetch error message
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In case of statement related errors, we need to pass the respective
statement handle to `SQLError()`.
Closes GH-6217.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.4:
Fix #80147: BINARY strings may not be properly zero-terminated
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.3:
Fix #80147: BINARY strings may not be properly zero-terminated
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We have to manually ensure that all strings fetched from a data source
are zero-terminated.
Closes GH-6213.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
These have been called qualifier and owner with ODBC 2, but ODBC 3
changed that to catalog and schema, respectively.
Closes GH-6210.
|
| | | |
|
| | |
| | |
| | |
| | | |
That bug has been fixed, so no need to keep that link any longer.
|
| | |
| | |
| | |
| | | |
Closes GH-6154
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.4:
Use proper skipif section
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.3:
Use proper skipif section
|
| | |
| | |
| | |
| | |
| | | |
The ODBC tests have to be skipped if no connection to the server can be
established.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.4:
Fix #78470: odbc_specialcolumns() no longer accepts $nullable
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.3:
Fix #78470: odbc_specialcolumns() no longer accepts $nullable
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
It is mandatory to pass either `SQL_NO_NULLS` or `SQL_NULLABLE` as
tenth parameter to `SQLSpecialColumns()`; otherwise the function call
fails. Therefore the user must be allowed to pass the desired value
as parameter to `odbc_specialcolumns()` again.
Closes GH-6200.
|
| | |
| | |
| | |
| | |
| | | |
That `bool(false)` is a relict of adapting the test expectations to the
warning promotions.
|
| | |
| | |
| | |
| | |
| | | |
This should fix most of the remaining issues with tabs and spaces
being mixed in tests.
|
| | |
| | |
| | |
| | | |
SQLCHAR* cast all the things.
|
| | | |
|
| | |
| | |
| | |
| | | |
Settling on using quoted string
|
| | |
| | |
| | |
| | | |
Closes GH-6123
|
| | |
| | |
| | |
| | | |
Closes GH-6034
|
| | | |
|
| | |
| | |
| | |
| | | |
Closes GH-5758
|