ID: 25112 User updated by: gms08701 at yahoo dot com Reported By: gms08701 at yahoo dot com Status: Open Bug Type: ODBC related Operating System: windows 2000 sp4 PHP Version: 4CVS-2003-08-16 (stable) New Comment:
Well Ill have to say, that was an excellent read. Appending 'FOR READ ONLY' after SELECT statements, seem to have circumvented the problem, and improve performance :) Thanks for the tip. For the PHP ODBC developers, the article made a few references to proposed fixes/workarounds. Page 17, first 2 paragraphs, talks about how PHP ODBC and DB2 talk, doing convertions. If its possible to have a switch so one can change the nature of a cursor would be great. And starting from the second to last paragraph on page 19 talks about datatypes that aren't supported by PHP ODBC, and a proposed fix. So Im going to continue fixing some more SQL, and see how the script does, but for now, it seems good. Sniper, I leave the bug status up to your descretion. Thanks Previous Comments: ------------------------------------------------------------------------ [2003-08-17 12:22:14] php at jschreiber dot com have you tried "SELECT [...] FOR READ ONLY"? all cursors are dynamic by default and there cursors are no longer supported in db/2 v8.1. have you read ibm's article on http://www7b.software.ibm.com/dmdd/library/techarticle/0301liu/0301liu.html ? it conains a lot of useful information on blob handling with db2 and php. ------------------------------------------------------------------------ [2003-08-17 08:10:08] gms08701 at yahoo dot com Yeah, that wouldn't work ;) Im open to other suggestions that anyone may have. Thanks for listening... ------------------------------------------------------------------------ [2003-08-17 01:05:14] [EMAIL PROTECTED] duh..disregard my previous comment, I didn't notice you're using windows.. :) ------------------------------------------------------------------------ [2003-08-17 01:04:41] [EMAIL PROTECTED] I was a bit too fast with the 'bogus' button. :) Anyway, I remember someone saying that even IBM themself suggest that you should actually use the UnixODBC instead of native DB2 driver..(have the library from http://www.unixodbc.org/ installed and configure with --with-unixODBC) Please try it out to see if it makes any difference. ------------------------------------------------------------------------ [2003-08-17 00:49:06] gms08701 at yahoo dot com I've been over that page already that you posted, but Im not sure how it applies. According to the code snippet I provided, if I comment out line 6 and uncomment line 5, I can then select the CLOB column via php. So even though the errors may be the same, the circumstances between this bug report and the page you provided aren't. Plus, the SQL works via DB2's command line, and not with php, so I don't think its a DB2 problem. So Im going to reopen it. If you still feel that its bogus, reset it as such, and Ill accept it as so. Thanks ------------------------------------------------------------------------ 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/25112 -- Edit this bug report at http://bugs.php.net/?id=25112&edit=1
