ID: 8941
Updated by: kalowsky
Reported By: [EMAIL PROTECTED]
Old-Status: Open
Status: Analyzed
Bug Type: ODBC related
Operating system: 
PHP Version: 4.0.2
Assigned To: 
Comments:

moving this to analyzed as hopefully once I work out this cursors patch it will be 
gone too!

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

[2001-05-09 16:32:57] [EMAIL PROTECTED]

this issue is specific to the interaction of the Progress database and the OpenLink 
Agent-based cursor library

once scrollable cursors are not used this is not a problem

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

[2001-04-02 17:01:59] [EMAIL PROTECTED]

According to openlink, the issue is caused by the dynamic cursors now used in the php 
odbc functions. 

remarking out the #define HAVE_SQL_EXTENDED_FETCH 1 entry in the iodbc section 
provides a temporary relief from the problem.                

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

[2001-04-02 16:55:47] [EMAIL PROTECTED]

have you tried updating to the latest OpenLink libraries?  They have supposedly been 
better enhanced and unified with PHP.

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

[2001-02-05 10:36:30] [EMAIL PROTECTED]

problem still exists in PHP 404 sp1

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

[2001-01-26 12:27:51] [EMAIL PROTECTED]

Configuration above should show PHP4.0.2 not 4.0.1pl2

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

The remainder of the comments for this report are too long.
To view the rest of the comments, please
view the bug report online.


ATTENTION! Do NOT reply to this email!
To reply, use the web interface found at http://bugs.php.net/?id=8941&edit=2


-- 
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to