| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
And tiny drive by refactor at the same time for more usages
|
|
|
|
| |
Related to GH-6701
|
|
|
|
| |
Closes GH-6691
|
|\
| |
| |
| |
| | |
* PHP-8.0:
Fix locale dependent parsing of PostgreSQL version number
|
| |\
| | |
| | |
| | |
| | | |
* PHP-7.4:
Fix locale dependent parsing of PostgreSQL version number
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Version numbers are not supposed to be localized, so we must not apply
locale dependent parsing with `atof()`.
Using `php_version_compare()` might even be better.
Closes GH-6668.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Historically, the _ex variants separated the zval first, if a
conversion was necessary. This distinction no longer makes sense
since PHP 7.
The only difference that was still left is that _ex checked whether
the type is the same first, but the usage of these macros did not
actually distinguish on whether such an inlined check is valuable
or not in a given context.
Also drop the unused convert_to_explicit_type macros.
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| | |
This testing mode executes the test multiple times in the same
process (but in different requests). It is primarily intended to
catch tracing JIT bugs, but also catches state leaks across
requests.
Closes GH-6365.
|
| |
| |
| |
| |
| |
| |
| | |
Make [] acceptable both for classes without constructors and
classes with a constructor that takes no arguments.
Closes GH-6336.
|
| |
| |
| |
| | |
Closes GH-6335
|
| |
| |
| |
| | |
These set the PGSQL_DML_EXEC flag by default.
|
| |
| |
| |
| |
| |
| |
| | |
This is an error that slipped in via 8d37c37bcdbf6fa99cd275413342457eeb2c664e.
pg_unescape_bytea() did not accept null in PHP 7.4, and it is not
meaningful for it to accept null now -- it will always fail, and now
with a misleading OOM message.
|
| |
| |
| |
| | |
Closes GH-6294.
|
| |
| |
| |
| | |
Closes 6260
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add some tests to cover related codepaths.
With the small caveat that the ones in build_assignment_string()
still don't seem to be tested as it looks the condtions are checked
beforehand, might need some more investigation.
Closes GH-6226
|
| |
| |
| |
| |
| | |
This makes it line up with pg_fetch_all_columns(), as well as
similar functions in other exts, such as mysqli_fetch_all().
|
| |
| |
| |
| |
| |
| |
| |
| | |
The same error condition is a ValueError in mysqli, be consistent.
Additionally, do not display the argument name for these errors.
As the signatures are overloaded, the argument name may not match
the meaning at all.
|
| |
| |
| |
| | |
This was already checked directly above.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The implementation did not check for PQunescapeBytea failure
correctly, because it checked for a null pointer after estrndup,
which certainly cannot happen. Inspection of the PGunescapeBytea
implementation has shown that this function can only fail on OOM,
so let's check for that explicitly and remove false as a possible
return type.
While we're here, avoid an unnecessary copy of the result.
|
| |
| |
| |
| |
| | |
These have been documentation-deprecated for a very long time,
make it official.
|
| |
| |
| |
| | |
Closes GH-6149
|
| |
| |
| |
| |
| |
| |
| | |
Do some drive by indentation fixes
Also fix pg_select() in regards to the $result_type arg which was missing from ZPP
Closes GH-6129
|
| |
| |
| |
| |
| |
| | |
For "field name or field offset" parameters.
Also make $ctor_params an ?array parameter.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
As the comment indicates, these are deprecated in PHP 4.2...
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
Also convert_libmagic_pattern() to return a zend_string*
Closes GH-6029
|
| | |
|
| |
| |
| |
| | |
Closes GH-5958
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
From an engine perspective, named parameters mainly add three
concepts:
* The SEND_* opcodes now accept a CONST op2, which is the
argument name. For now, it is looked up by linear scan and
runtime cached.
* This may leave UNDEF arguments on the stack. To avoid having
to deal with them in other places, a CHECK_UNDEF_ARGS opcode
is used to either replace them with defaults, or error.
* For variadic functions, EX(extra_named_params) are collected
and need to be freed based on ZEND_CALL_HAS_EXTRA_NAMED_PARAMS.
RFC: https://wiki.php.net/rfc/named_params
Closes GH-5357.
|
| |
| |
| |
| |
| | |
And make sure too few/many arguments throws, to satisfy the
function signature.
|
| | |
|
| |
| |
| |
| | |
These functions don't do anything special, just use normal zpp.
|
| | |
|
| |
| |
| |
| | |
Closes GH-5758
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Even if that header file is available, we better consider it private,
and don't include it. The information about whether SSL support is
enabled is now missing (`USE_(OPEN)SSL`), and it seems there is no
alternative way to get it (`PQinitSSL()` is always defined), so we
remove it from the PHP info. Furthermore, the `PG_VERSION` and
`PG_VERSION_STR` macros are no longer available, but as of libpq 9.1
there is `PQlibVersion()` which allows us to construct `PG_VERSION` in
a most likely backwards compatible manner. The additional information
available through `PG_VERSION_STR` is lost, though, so we define
`PGSQL_LIBPQ_VERSION_STR` basically as alias of `PGSQL_LIBPQ_VERSION`,
and deprecate it right away.
Since we are now requiring at least libpq 9.1, we can remove some
further compatibility code and additional checks.
Regarding the raised requirements: official support for PostGreSQL 9.0
ended on 2015-10-08, and even CentOS 7 already has PostGreSQL 9.2, so
this is not supposed to be too much of an issue.
|
| |
| |
| |
| |
| |
| |
| | |
We can safely assume that users have at the very least libpq 7.4, for
which official support ended on 2010-10-01; even CentOS 6 has 8.4 now.
It is also noteworthy that PDO_PGSQL already requires libpq 7.4 or
later.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
From now on, float to string casting will always behave locale-independently.
RFC: https://wiki.php.net/rfc/locale_independent_float_to_string
Closes GH-5224
Co-authored-by: George Peter Banyard <girgias@php.net>
|
|\ \
| |/
| |
| |
| | |
* PHP-7.4:
Fix #79532: sizeof off_t can be wrong
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We have to actually determine the proper `SIZEOF_OFF_T`.
Interestingly, it is `4` on Windows x64.
We also have to prevent the redefinition in pg_config.h. The clean
solution would likely be to not include pg_config.h at all, but that's
out of scope for BC reasons for now.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Instead add RETURN_COPY(_VALUE) macros will the expected behavior.
RETURN_ZVAL doesn't make any sense since PHP 7, but has stuck
around, probably because the alternative was to write directly to
the return_value variable.
|
| |
| |
| |
| | |
Closes GH-5066 As a first step, let's capitalize their initial letter when it is applicable.
|
| | |
|