|
php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login |
PatchesPull RequestsHistoryAllCommentsChangesGit/SVN commits
[2020-03-03 11:53 UTC] marcel at wieland dot koeln
[2020-03-04 12:24 UTC] tobias dot john at foo dot ag
[2021-08-09 14:03 UTC] cmb@php.net
-Status: Open
+Status: Verified
-Type: Bug
+Type: Documentation Problem
[2021-08-09 14:03 UTC] cmb@php.net
[2021-11-11 11:33 UTC] git@php.net
[2021-11-11 11:33 UTC] git@php.net
-Status: Verified
+Status: Closed
|
|||||||||||||||||||||||||||||||||||||
Copyright © 2001-2025 The PHP GroupAll rights reserved. |
Last updated: Tue Oct 28 00:00:02 2025 UTC |
Description: ------------ When selecting data from a PostgreSQL database using quoted aliases for column names (to preserve case, for example), pg_field_num() seems to expect its input to also contain double quotes. However, returned values from functions like pg_field_name() and pg_fetch_assoc() do not contain double quotes. PostgreSQL's own client also does not include double quotes in the resulting column names. Even if the behavior of pg_field_num is intentional, there does not seem to be a way to determine if field aliases have been quoted using the result resource only. I suggest fixing pg_field_num() so that it is consistent with the other PostgreSQL functions. I would expect the function to accept the actual field name, not encapsulated in double quotes. Test script: --------------- $result = pg_query('SELECT \'test\' AS "TeSt"'); var_dump(pg_field_name($result, 0)); // returns TeSt var_dump(pg_field_num($result, 'TeSt')); // returns -1 (error) var_dump(pg_field_num($result, '"TeSt"')); // returns 0 (first column) Expected result: ---------------- I expect pg_field_num($result, 'TeSt') to return 0 instead of an error. Actual result: -------------- -1