#23146 [Ana->Fbk]: odbc_result column 1 empty after first use
| From: | sniper@php.net | Date: | Thu, 15 May 2003 18:29:29 +0000 |
| Subject: | #23146 [Ana->Fbk]: odbc_result column 1 empty after first use | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-39728@lists.php.net to get a copy of this message | ||
ID: 23146
Updated by: sniper@php.net
Reported By: wohlfarth dot m at web dot de
-Status: Analyzed
+Status: Feedback
Bug Type: ODBC related
Operating System: Win2k SP2
PHP Version: 4.3.2-RC
Previous Comments:
------------------------------------------------------------------------
[2003-04-24 07:41:01] kalowsky@php.net
Just to make sure, this is using the example you've posted above, not
some deviation, right?
------------------------------------------------------------------------
[2003-04-24 03:22:07] wohlfarth dot m at web dot de
Complete Logfile is very long, here is the part of interest:
750-b24 ENTER SQLGetData
HSTMT 00EC1DB0
UWORD 9
SWORD 1 <SQL_C_CHAR>
PTR 0x053E8620
SQLLEN 4096
SQLLEN * 0x0595C5E4
750-b24 EXIT SQLGetData with return code 0
(SQL_SUCCESS)
HSTMT 00EC1DB0
UWORD 9
SWORD 1 <SQL_C_CHAR>
PTR 0x053E8620 [ 11] "521 (70074)" --> first
odbc_result here
SQLLEN 4096
SQLLEN * 0x0595C5E4 (11)
750-b24 ENTER SQLGetData
HSTMT 00EC1DB0
UWORD 9
SWORD 1 <SQL_C_CHAR>
PTR 0x053E9638
SQLLEN 4096
SQLLEN * 0x0595C5E4
750-b24 EXIT SQLGetData with return code 100
(SQL_NO_DATA_FOUND) --> ERROR here ???
HSTMT 00EC1DB0
UWORD 9
SWORD 1 <SQL_C_CHAR>
PTR 0x053E9638
SQLLEN 4096
SQLLEN * 0x0595C5E4
750-b24 ENTER SQLExtendedFetch
HSTMT 00EC1DB0
UWORD 1 <SQL_FETCH_NEXT>
SQLROWOFFSET 1
SQLROWSETSIZE * 0x0520F318
UWORD * 0x0520F320
750-b24 EXIT SQLExtendedFetch with return code 0
(SQL_SUCCESS)
HSTMT 00EC1DB0
UWORD 1 <SQL_FETCH_NEXT>
SQLROWOFFSET 1
SQLROWSETSIZE * 0x0520F318 (1)
UWORD * 0x0520F320 (0)
------------------------------------------------------------------------
[2003-04-23 11:10:21] kalowsky@php.net
Don't mind sniper, he's a little over-zealous with the bogus-ification.
You're correct though that SELECT DISTINCT does create problems with
the ODBC system at the moment. I haven't yet been able to figure out
why.
Any chance you can create a log of the SQL transactions (SQL Log option
on your ODBC Administrator) and post it here?
------------------------------------------------------------------------
[2003-04-23 05:20:41] wohlfarth dot m at web dot de
Here still a few information to the problem:
- Database: Sybase Anywhere Version 7
- Webserver: Apache 2.0 with OpenSSL
- ODBC: Version 3.520
In the meantime I found still out that the problem arises, if the
column from a Subquery were
produced.
Query sample:
select distinct a.column1, a.column2,
(select List(b.column1) from Table2 as b
where b.Prim = a.Prim) as ListColumn
from Table1 as a
where a.Prim = 1
------------------------------------------------------------------------
[2003-04-10 04:04:45] wohlfarth dot m at web dot de
$idresult2 = odbc_exec($iddb, $sqlqry2);
odbc_fetch_row($idresult2);
// Column 1 contains a string
if ( odbc_result($idresult2, 1) <> "" ) {
// Column 1 is now empty
echo odbc_result($idresult2, 1);
};
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=23146&edit=1