php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #72058 pg_field_num Error with Quoted Aliases
Submitted: 2016-04-19 12:56 UTC Modified: -
Votes:1
Avg. Score:5.0 ± 0.0
Reproduced:1 of 1 (100.0%)
Same Version:1 (100.0%)
Same OS:1 (100.0%)
From: klaxian at gmail dot com Assigned:
Status: Open Package: PostgreSQL related
PHP Version: 5.5.34 OS: Debian Linux
Private report: No CVE-ID: None
Have you experienced this issue?
Rate the importance of this bug to you:

 [2016-04-19 12:56 UTC] klaxian at gmail dot com
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

Patches

Add a Patch

Pull Requests

Add a Pull Request

 
PHP Copyright © 2001-2019 The PHP Group
All rights reserved.
Last updated: Fri Dec 06 11:01:25 2019 UTC