|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #16782 PHP & libiodbc-3.0.5 return garbage column names with ingres
Submitted: 2002-04-23 21:23 UTC Modified: 2002-04-24 11:27 UTC
Avg. Score:3.0 ± 0.0
Reproduced:0 of 1 (0.0%)
From: karlm at isd dot canberra dot edu dot au Assigned:
Status: Not a bug Package: ODBC related
PHP Version: 4.2.0 OS: Solaris 8
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
Block user comment
Status: Assign to:
Bug Type:
From: karlm at isd dot canberra dot edu dot au
New email:
PHP Version: OS:


 [2002-04-23 21:23 UTC] karlm at isd dot canberra dot edu dot au
Use odbc_result_all or odbc_field_name to get the column names from odbc_exec  call to an ingres_ii database via libiodbc-3.0.5. The resulting column names are in fact portions of the original SQL query! Referencing by column number works.

I am unable to test this with another database via libiodbc, however I can reproduce it using two different ODBC drivers. Using the php native drivers to ingres does work (but is of course still experimental).

Configure line below:

./configure --with-ldap=/usr/local/ --enable-libgcc --enable-ftp --with-mysql=/usr/local/mysql --with-ingres=/db/ingres --with-iodbc=/usr/local/src/libiodbc-3.0.5 --enable-discard-path --enable-wddx --enable-track-vars --enable-sysvsem --with-nsapi=/db/www/netscape/server4 --with-oci8=/oracle/home/product/8.1.7


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2002-04-24 11:04 UTC]
Please enter this into a support case at

A client-side trace would be helpful as well.

Best regards,
Andrew Hill
 [2002-04-24 11:27 UTC]
The bug system is not the appropriate forum for asking support
questions. For a list of a range of more appropriate places to ask
for help using PHP, please visit

sounds like it's an OpenLink issue.
PHP Copyright © 2001-2022 The PHP Group
All rights reserved.
Last updated: Sun May 22 20:05:44 2022 UTC