ID: 8941 User Update by: [EMAIL PROTECTED] Old-Status: Feedback Status: Open Bug Type: ODBC related Description: Openlink/ODBC cannot parse complex queries 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. Previous Comments: --------------------------------------------------------------------------- [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 --------------------------------------------------------------------------- [2001-01-26 12:26:10] [EMAIL PROTECTED] Platform: HPUX 10.20 Configuration: PHP4.0.1pl2 --with-iodbc --without-mysql --with-pdflib=/usr/local --without-gd --with-apache=../apache_1.3.14 Using Openlink MT ODBC driver against a PROGRESS database. Any version of PHP after 4.0.1pl2 cannot parse queries with a JOIN statement in it. Versions upto and including above work ok. The log file from the Openlink Server shows this from a sample (good) query: generic_pro83b: SCR_AnalyseSQL failed: SELECT * FROM VIRTUAL_LAYERS INNER JOIN LAYER_INFORMATION ON LAYER_INFORMATION.LAYER1_DESCRIPTION=VIRTUAL_LAYERS.LAYER1_DESCRIPTION generic_pro83b: parse error generic_pro83b: SELECT * FROM VIRTUAL_LAYERS INNER JOIN^ --------------------------------------------------------------------------- Full Bug description available at: http://bugs.php.net/?id=8941 -- 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]
