summaryrefslogtreecommitdiff
path: root/ext/pgsql
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'PHP-7.2' into PHP-7.3Nikita Popov2019-04-101-3/+5
|\
| * Fix 29nb_async_connect.phptNikita Popov2019-04-101-3/+5
| | | | | | | | | | Intermediate states are unreliable across versions (I think), make sure we go through the whole connect procedure.
* | Merge branch 'PHP-7.2' into PHP-7.3Nikita Popov2019-04-103-8/+46
|\ \ | |/
| * Fix pgsql use after free trying to reuse closed connectionNikita Popov2019-04-103-8/+46
| | | | | | | | | | | | | | | | | | | | | | When a connection is closed, we also need to remove the hash entry from the regular_list, as it now points to freed memory. To do this store a reverse mapping from the connection to the hash string. It would be nicer to introduce a wrapping structure for the pgsql link resource that could store the hash (and notices), but that would require large changes to the extension, so I'm going for a more minimal fix here.
* | Merge branch 'PHP-7.2' into PHP-7.3Nikita Popov2019-04-102-5/+22
|\ \ | |/
| * Fix use after free on pg_close() of default connectionNikita Popov2019-04-102-5/+22
| |
| * Merge branch 'PHP-7.1' into PHP-7.2Anatol Belski2018-11-182-1/+41
| |\ | | | | | | | | | | | | * PHP-7.1: Fixed bug #77047 pg_convert has a broken regex for the 'TIME WITHOUT TIMEZONE' data type
| | * Fixed bug #77047 pg_convert has a broken regex for the 'TIME WITHOUT ↵Anatol Belski2018-11-182-1/+41
| | | | | | | | | | | | | | | | | | TIMEZONE' data type Backport 369c991d and 282a63da to 7.1, closes #3634
| | * Sync leading and final newlines in *.phpt sectionsPeter Kokot2018-10-1513-14/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds missing newlines, trims multiple redundant final newlines into a single one, and trims redundant leading newlines in all *.phpt sections. According to POSIX, a line is a sequence of zero or more non-' <newline>' characters plus a terminating '<newline>' character. [1] Files should normally have at least one final newline character. C89 [2] and later standards [3] mention a final newline: "A source file that is not empty shall end in a new-line character, which shall not be immediately preceded by a backslash character." Although it is not mandatory for all files to have a final newline fixed, a more consistent and homogeneous approach brings less of commit differences issues and a better development experience in certain text editors and IDEs. [1] http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_206 [2] https://port70.net/~nsz/c/c89/c89-draft.html#2.1.1.2 [3] https://port70.net/~nsz/c/c99/n1256.html#5.1.1.2
| | * Trim trailing whitespace in *.phptPeter Kokot2018-10-1420-67/+67
| | |
| | * Sync leading and final newlines in source code filesPeter Kokot2018-10-143-4/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds missing newlines, trims multiple redundant final newlines into a single one, and trims redundant leading newlines. According to POSIX, a line is a sequence of zero or more non-' <newline>' characters plus a terminating '<newline>' character. [1] Files should normally have at least one final newline character. C89 [2] and later standards [3] mention a final newline: "A source file that is not empty shall end in a new-line character, which shall not be immediately preceded by a backslash character." Although it is not mandatory for all files to have a final newline fixed, a more consistent and homogeneous approach brings less of commit differences issues and a better development experience in certain text editors and IDEs. [1] http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_206 [2] https://port70.net/~nsz/c/c89/c89-draft.html#2.1.1.2 [3] https://port70.net/~nsz/c/c99/n1256.html#5.1.1.2
| | * Trim trailing whitespace in source code filesPeter Kokot2018-10-134-49/+49
| | |
| | * Convert CRLF line endings to LFPeter Kokot2018-10-131-78/+78
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch simplifies line endings tracked in the Git repository and syncs them to all include the LF style instead of the CRLF files. Newline characters: - LF (\n) (*nix and Mac) - CRLF (\r\n) (Windows) - CR (\r) (old Mac, obsolete) To see which line endings are in the index and in the working copy the following command can be used: `git ls-files --eol` Git additionally provides `.gitattributes` file to specify if some files need to have specific line endings on all platforms (either CRLF or LF). Changed files shouldn't cause issues on modern Windows platforms because also Git can do output conversion is core.autocrlf=true is set on Windows and use CRLF newlines in all files in the working tree. Unless CRLF files are tracked specifically, Git by default tracks all files in the index using LF newlines.
| * | Sync leading and final newlines in *.phpt sectionsPeter Kokot2018-10-1513-14/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds missing newlines, trims multiple redundant final newlines into a single one, and trims redundant leading newlines in all *.phpt sections. According to POSIX, a line is a sequence of zero or more non-' <newline>' characters plus a terminating '<newline>' character. [1] Files should normally have at least one final newline character. C89 [2] and later standards [3] mention a final newline: "A source file that is not empty shall end in a new-line character, which shall not be immediately preceded by a backslash character." Although it is not mandatory for all files to have a final newline fixed, a more consistent and homogeneous approach brings less of commit differences issues and a better development experience in certain text editors and IDEs. [1] http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_206 [2] https://port70.net/~nsz/c/c89/c89-draft.html#2.1.1.2 [3] https://port70.net/~nsz/c/c99/n1256.html#5.1.1.2
| * | Trim trailing whitespace in *.phptPeter Kokot2018-10-1420-67/+67
| | |
| * | Sync leading and final newlines in source code filesPeter Kokot2018-10-143-4/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds missing newlines, trims multiple redundant final newlines into a single one, and trims redundant leading newlines. According to POSIX, a line is a sequence of zero or more non-' <newline>' characters plus a terminating '<newline>' character. [1] Files should normally have at least one final newline character. C89 [2] and later standards [3] mention a final newline: "A source file that is not empty shall end in a new-line character, which shall not be immediately preceded by a backslash character." Although it is not mandatory for all files to have a final newline fixed, a more consistent and homogeneous approach brings less of commit differences issues and a better development experience in certain text editors and IDEs. [1] http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_206 [2] https://port70.net/~nsz/c/c89/c89-draft.html#2.1.1.2 [3] https://port70.net/~nsz/c/c99/n1256.html#5.1.1.2
| * | Trim trailing whitespace in source code filesPeter Kokot2018-10-134-49/+49
| | |
* | | Add test for bug #77047Anatol Belski2018-11-181-0/+40
| | |
* | | FIX #77047: fixes regex for "time" data typeandy2018-11-181-1/+1
| | |
* | | Future-proof email addressesZeev Suraski2018-11-012-2/+2
| | |
* | | Sync leading and final newlines in *.phpt sectionsPeter Kokot2018-10-1513-14/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds missing newlines, trims multiple redundant final newlines into a single one, and trims redundant leading newlines in all *.phpt sections. According to POSIX, a line is a sequence of zero or more non-' <newline>' characters plus a terminating '<newline>' character. [1] Files should normally have at least one final newline character. C89 [2] and later standards [3] mention a final newline: "A source file that is not empty shall end in a new-line character, which shall not be immediately preceded by a backslash character." Although it is not mandatory for all files to have a final newline fixed, a more consistent and homogeneous approach brings less of commit differences issues and a better development experience in certain text editors and IDEs. [1] http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_206 [2] https://port70.net/~nsz/c/c89/c89-draft.html#2.1.1.2 [3] https://port70.net/~nsz/c/c99/n1256.html#5.1.1.2
* | | Trim trailing whitespace in *.phptPeter Kokot2018-10-1420-67/+67
| | |
* | | Sync leading and final newlines in source code filesPeter Kokot2018-10-143-4/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds missing newlines, trims multiple redundant final newlines into a single one, and trims redundant leading newlines. According to POSIX, a line is a sequence of zero or more non-' <newline>' characters plus a terminating '<newline>' character. [1] Files should normally have at least one final newline character. C89 [2] and later standards [3] mention a final newline: "A source file that is not empty shall end in a new-line character, which shall not be immediately preceded by a backslash character." Although it is not mandatory for all files to have a final newline fixed, a more consistent and homogeneous approach brings less of commit differences issues and a better development experience in certain text editors and IDEs. [1] http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_206 [2] https://port70.net/~nsz/c/c89/c89-draft.html#2.1.1.2 [3] https://port70.net/~nsz/c/c99/n1256.html#5.1.1.2
* | | Trim trailing whitespace in source code filesPeter Kokot2018-10-133-47/+47
| | |
* | | Trim trailing whitespaces in build filesPeter Kokot2018-07-291-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | Some editors utilizing .editorconfig automatically trim whitespaces. For convenience this patch removes whitespaces in certain build files: - ext/*/config*.m4 - configure.ac - acinclude.m4
* | | Fix typos in code commentsPeter Kokot2018-07-251-1/+1
| | |
* | | Remove unused Git attributes identPeter Kokot2018-07-254-8/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The $Id$ keywords were used in Subversion where they can be substituted with filename, last revision number change, last changed date, and last user who changed it. In Git this functionality is different and can be done with Git attribute ident. These need to be defined manually for each file in the .gitattributes file and are afterwards replaced with 40-character hexadecimal blob object name which is based only on the particular file contents. This patch simplifies handling of $Id$ keywords by removing them since they are not used anymore.
* | | Reduce error buffer sizeAnatol Belski2018-07-051-1/+1
| | | | | | | | | | | | 120 bytes is ample, the doc says.
* | | Use zval_ptr_dtor() imstead of zval_dtor()Dmitry Stogov2018-07-051-2/+2
| | |
* | | Replace legacy zval_dtor() by zval_ptr_dtor_nogc() or even more specialized ↵Dmitry Stogov2018-07-041-7/+7
| | | | | | | | | | | | | | | | | | | | | destructors. zval_dtor() doesn't make a lot of sense in PHP-7.* and it's used incorrectly in some places. Its occurances should be replaced by zval_ptr_dtor() or zval_ptr_dtor_nogc(), or even more specialized destructors.
* | | Merge branch 'PHP-7.2'Anatol Belski2018-06-292-0/+24
|\ \ \ | |/ / | | | | | | | | | * PHP-7.2: Fixed bug #76548 pg_fetch_result did not fetch the next row
| * | Merge branch 'PHP-7.1' into PHP-7.2Anatol Belski2018-06-292-0/+24
| |\ \ | | |/ | | | | | | | | | * PHP-7.1: Fixed bug #76548 pg_fetch_result did not fetch the next row
| | * Fixed bug #76548 pg_fetch_result did not fetch the next rowAnatol Belski2018-06-292-0/+24
| | |
* | | Removed "dead" code (zend_hash_update() never fails)Dmitry Stogov2018-06-011-3/+1
| | |
* | | Avoid useless checks, using zend_string_efree(), in cases where the string ↵Dmitry Stogov2018-05-081-1/+1
| | | | | | | | | | | | is known to be a temporary allocated zend_string.
* | | zend_fcall_info_cache.calling_scope is not used by zend_call_function() and ↵Dmitry Stogov2018-05-031-1/+0
| | | | | | | | | | | | | | | | | | doesn't have to be initialized. It's used only as a result of zend_is_callable() in forward_static_call and spl_autoload.
* | | Avoid strlen calls for regexesAnatol Belski2018-04-191-45/+63
| | |
* | | Use int instead of long in protosGabriel Caruso2018-02-231-2/+2
| | |
* | | Use EXPECT instead of EXPECTF when possibleGabriel Caruso2018-02-203-3/+3
| | | | | | | | | | | | EXPECTF logic in run-tests.php is considerable, so let's avoid it.
* | | Reduce var scopeAnatol Belski2018-02-181-32/+24
| | |
* | | Remove empty sections in testsGabriel Caruso2018-02-141-1/+0
| | |
* | | Fix misspelling vlaues to valuesGabriel Caruso2018-01-281-1/+1
| | |
* | | Merge branch 'PHP-7.2'Xinchen Hui2018-01-181-0/+1
|\ \ \ | |/ / | | | | | | | | | | | | * PHP-7.2: Updated NEWS Fixed #75838 (Memory leak in pg_escape_bytea())
| * | Merge branch 'PHP-7.1' into PHP-7.2Xinchen Hui2018-01-181-0/+1
| |\ \ | | |/ | | | | | | | | | * PHP-7.1: Fixed #75838 (Memory leak in pg_escape_bytea())
| | * Fixed #75838 (Memory leak in pg_escape_bytea())Xinchen Hui2018-01-181-0/+1
| | |
| | * year++Xinchen Hui2018-01-022-2/+2
| | |
| * | year++Xinchen Hui2018-01-022-2/+2
| | |
* | | Avoid separation and simlifyed conversionDmitry Stogov2018-01-171-25/+12
| | |
* | | year++Xinchen Hui2018-01-022-2/+2
| | |
* | | zend_fcall_info_cache.initialized is removed (zend_fcall_info_cache is ↵Dmitry Stogov2017-12-271-1/+0
| | | | | | | | | | | | initialized if zend_fcall_info_cache.function_handler is set).
View Lorry Controller Status