#23146 [Fbk->Opn]: odbc_result column 1 empty after first use

From: Date: Mon, 26 May 2003 08:15:36 +0000
Subject: #23146 [Fbk->Opn]: odbc_result column 1 empty after first use
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-40424@lists.php.net to get a copy of this message 
 ID:               23146
 User updated by:  wohlfarth dot m at web dot de
 Reported By:      wohlfarth dot m at web dot de
-Status:           Feedback
+Status:           Open
 Bug Type:         ODBC related
 Operating System: Win2k SP2
 PHP Version:      4.3.2-RC
 New Comment:

Please apology for the long waiting period...

Right !

I learned in the meantime that this can be produced in different ways.
I could cause the effect with List(ColumnX) and with a Subquery as
column. I suppose the error occurs, when the fieldtype is not defined
by a field from a table of the database.


Previous Comments:
------------------------------------------------------------------------

[2003-05-25 21:55:48] sniper@php.net

...another week goes by without the feedback..


------------------------------------------------------------------------

[2003-05-20 12:32:21] sniper@php.net

..still waiting for feedback..


------------------------------------------------------------------------

[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?

------------------------------------------------------------------------

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
    http://bugs.php.net/23146

-- 
Edit this bug report at http://bugs.php.net/?id=23146&edit=1

Thread (14 messages)

« previous php.bugs (#40424) next »