#
6ac3f7c8 |
| 05-Sep-2022 |
Yurun |
Fix GH-9411: PgSQL large object resource is incorrectly closed Co-authored-by: Christoph M. Becker <cmbecker69@gmx.de> Closes GH-9411.
|
#
778513f6 |
| 05-Dec-2021 |
SATO Kentaro |
Fix error message allocation of PDO PgSQL Closes GH-7723.
|
#
a5527577 |
| 10-Dec-2020 |
Nikita Popov |
Allow drivers to omit error code And thus generate error messages that match what PDO emulation would generate. This fixes the error message regression from the previous commit.
|
Revision tags: php-8.0.0, php-7.3.25, php-7.4.13, php-8.0.0RC5, php-7.4.13RC1, php-8.0.0RC4, php-7.3.25RC1, php-7.4.12, php-8.0.0RC3, php-7.3.24, php-8.0.0RC2, php-7.4.12RC1, php-7.3.24RC1, php-7.2.34, php-8.0.0rc1, php-7.4.11, php-7.3.23 |
|
#
b4c2670f |
| 18-Sep-2020 |
Máté Kocsis |
Fix UNKNOWN default values in ext/pdo_pgsql Closes GH-6159
|
Revision tags: php-8.0.0beta4, php-7.4.11RC1, php-7.3.23RC1 |
|
#
48368a6b |
| 12-Sep-2020 |
George Peter Banyard |
Promote Warnings to Error in PostgreSQL PDO driver Closes GH-6119
|
Revision tags: php-8.0.0beta3, php-7.4.10, php-7.3.22 |
|
#
44ade0e8 |
| 31-Aug-2020 |
Matteo Beccati |
Fix #80027 Terrible performance using $query->fetch on queries with many bind parameters Added new flags that allow skipping param_evt(s) that are not used by drivers, in a backwards and
Fix #80027 Terrible performance using $query->fetch on queries with many bind parameters Added new flags that allow skipping param_evt(s) that are not used by drivers, in a backwards and forward compatible manner. Updated the pgsql, mysql, sqlite and oci drivers to properly use the new flags. I've left out pdo_dblib, which doesn't have a param_hook, and pdo_firebird, which seems to be using PARAM_EVT_NORMALIZE in a wrong context (param type vs event type).
show more ...
|
#
ee2506cc |
| 31-Aug-2020 |
Matteo Beccati |
Fix #80027 Terrible performance using $query->fetch on queries with many bind parameters Added new flags that allow skipping param_evt(s) that are not used by drivers, in a backwards and
Fix #80027 Terrible performance using $query->fetch on queries with many bind parameters Added new flags that allow skipping param_evt(s) that are not used by drivers, in a backwards and forward compatible manner. Updated the pgsql, mysql, sqlite and oci drivers to properly use the new flags. I've left out pdo_dblib, which doesn't have a param_hook, and pdo_firebird, which seems to be using PARAM_EVT_NORMALIZE in a wrong context (param type vs event type).
show more ...
|
Revision tags: php-8.0.0beta2, php-7.3.22RC1, php-7.4.10RC1, php-8.0.0beta1, php-7.4.9, php-7.2.33, php-7.3.21, php-8.0.0alpha3, php-7.4.9RC1, php-7.3.21RC1, php-7.4.8, php-7.2.32, php-8.0.0alpha2, php-7.3.20, php-8.0.0alpha1, php-7.4.8RC1, php-7.3.20RC1, php-7.4.7, php-7.3.19, php-7.4.7RC1, php-7.3.19RC1, php-7.4.6, php-7.2.31, php-7.4.6RC1, php-7.3.18RC1, php-7.2.30, php-7.4.5, php-7.3.17, php-7.4.5RC1, php-7.3.17RC1, php-7.3.18, php-7.4.4, php-7.2.29, php-7.3.16, php-7.4.4RC1, php-7.3.16RC1, php-7.4.3, php-7.2.28, php-7.3.15RC1, php-7.4.3RC1, php-7.3.15, php-7.2.27, php-7.4.2, php-7.3.14, php-7.3.14RC1, php-7.4.2RC1, php-7.4.1, php-7.2.26, php-7.3.13, php-7.4.1RC1, php-7.3.13RC1, php-7.2.26RC1, php-7.4.0, php-7.2.25, php-7.3.12, php-7.4.0RC6, php-7.3.12RC1, php-7.2.25RC1, php-7.4.0RC5, php-7.1.33, php-7.2.24, php-7.3.11, php-7.4.0RC4, php-7.3.11RC1, php-7.2.24RC1, php-7.4.0RC3, php-7.2.23, php-7.3.10, php-7.4.0RC2, php-7.2.23RC1, php-7.3.10RC1, php-7.4.0RC1, php-7.1.32, php-7.2.22, php-7.3.9, php-7.4.0beta4, php-7.2.22RC1, php-7.3.9RC1, php-7.4.0beta2, php-7.1.31, php-7.2.21, php-7.3.8, php-7.4.0beta1, php-7.2.21RC1, php-7.3.8RC1, php-7.4.0alpha3, php-7.3.7, php-7.2.20, php-7.4.0alpha2, php-7.3.7RC3, php-7.3.7RC2, php-7.2.20RC2, php-7.4.0alpha1, php-7.3.7RC1, php-7.2.20RC1, php-7.2.19, php-7.3.6, php-7.1.30, php-7.2.19RC1, php-7.3.6RC1, php-7.1.29, php-7.2.18, php-7.3.5, php-7.2.18RC1, php-7.3.5RC1, php-7.2.17, php-7.3.4, php-7.1.28, php-7.3.4RC1, php-7.2.17RC1, php-7.1.27, php-7.3.3, php-7.2.16, php-7.3.3RC1, php-7.2.16RC1 |
|
#
2fe2e5b4 |
| 17-Feb-2019 |
Ahmed Abdou |
Fix #64705 errorInfo property of PDOException is null when PDO::__construct() fails PDO driver constructors are throwing PdoException without setting errorInfo, so create a new reusable
Fix #64705 errorInfo property of PDOException is null when PDO::__construct() fails PDO driver constructors are throwing PdoException without setting errorInfo, so create a new reusable function that throws exceptions for PDO and will also set the errorInfo. Use this function in pdo_mysql, pdo_sqlite, and pdo_pgsql.
show more ...
|
#
4dd8fec0 |
| 21-Jul-2020 |
Nikita Popov |
Add stubs for PDO PGSql extension methods
|
#
2b5de6f8 |
| 01-Jul-2020 |
Max Semenik |
Remove proto comments from C files Closes GH-5758
|
#
ce668c0e |
| 25-May-2020 |
Christoph M. Becker |
PGSQL and POD_SQL: don't include pg_config.h Even if that header file is available, we better consider it private, and don't include it. The information about whether SSL support is
PGSQL and POD_SQL: don't include pg_config.h 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.
show more ...
|
#
c85ded76 |
| 20-May-2020 |
George Peter Banyard |
Fix [-Wundef] warning in PDO PostgreSQL extension
|
#
67f9b0b7 |
| 28-Apr-2020 |
Christoph M. Becker |
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
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.
show more ...
|
#
d1764ca3 |
| 15-Jan-2020 |
Máté Kocsis |
Make error messages more consistent by fixing capitalization Closes GH-5066 As a first step, let's capitalize their initial letter when it is applicable.
|
#
0b4778c3 |
| 16-Jan-2020 |
Máté Kocsis |
Fix #78880: Another bunch of spelling errors
|
#
7b4a4d2a |
| 03-Jan-2020 |
Máté Kocsis |
Use RETURN_THROWS() after try_convert_to_string()
|
#
34570372 |
| 31-Dec-2019 |
Máté Kocsis |
Use RETURN_THROWS() during ZPP in most of the extensions Except for some bigger ones: reflection, sodium, spl
|
#
37d11d12 |
| 17-Dec-2019 |
SATO Kentaro |
Fix #78982: pdo_pgsql returns dead persistent connection Call PQconsumeInput() before PQstatus() to update the status.
|
#
7e39e693 |
| 17-Dec-2019 |
SATO Kentaro |
Fix #78980: pgsqlGetNotify() overlooks dead connection pgsqlGetNotify() didn't check result of PQconsumeInput().
|
#
2204dbde |
| 31-Oct-2019 |
Máté Kocsis |
Add missing ZPP checks Closes GH-4878.
|
#
94938934 |
| 29-Oct-2019 |
Máté Kocsis |
Cleanup return values when parameter parsing is unsuccessful
|
#
5d6e923d |
| 24-Sep-2019 |
Gabriel Caruso |
Remove mention of PHP major version in Copyright headers Closes GH-4732.
|
#
b19fdc18 |
| 22-Jul-2019 |
Matteo Beccati |
Fix FR #71885 (Allow escaping question mark placeholders)
|
#
d59aac58 |
| 18-Jul-2019 |
Nikita Popov |
Report errors from stream read and write operations The php_stream_read() and php_stream_write() functions now return an ssize_t value, with negative results indicating failure. Function
Report errors from stream read and write operations The php_stream_read() and php_stream_write() functions now return an ssize_t value, with negative results indicating failure. Functions like fread() and fwrite() will return false in that case. As a special case, EWOULDBLOCK and EAGAIN on non-blocking streams should not be regarded as error conditions, and be reported as successful zero-length reads/writes instead. The handling of EINTR remains unclear and is internally inconsistent (e.g. some code-paths will automatically retry on EINTR, while some won't). I'm landing this now to make sure the stream wrapper ops API changes make it into 7.4 -- however, if the user-facing changes turn out to be problematic we have the option of clamping negative returns to zero in php_stream_read() and php_stream_write() to restore the old behavior in a relatively non-intrusive manner.
show more ...
|
#
a31f4642 |
| 26-Feb-2019 |
Nikita Popov |
Allow exceptions in __toString() RFC: https://wiki.php.net/rfc/tostring_exceptions And convert some object to string conversion related recoverable fatal errors into Error excep
Allow exceptions in __toString() RFC: https://wiki.php.net/rfc/tostring_exceptions And convert some object to string conversion related recoverable fatal errors into Error exceptions. Improve exception safety of internal code performing string conversions.
show more ...
|