Bug #25112 [Com]: SQLExecDirect error with CLOB column in SQL

Edit report at https://bugs.php.net/bug.php?id=25112&edit=1 ID: 25112 Comment by: lildurk25112 at gmail dot com Reported by: gms08701 at yahoo dot com Summary: SQLExecDirect error with CLOB column in SQL Status: Closed Type: Bug Package: ODBC related Operating System: windows 2000 sp4 PHP Version: 4CVS-2003-08-16 (stable) Block user comment: N Private report: N New Comment: Lil Durk is a private agency dedicated to providing responsible access to legal cannabis for adults aged 19 and older. We’re an exclusively online retailer and wholesaler for recreational cannabis and a trusted source for information about cannabis and cannabis-related issues. We believe our work is meaningful and we take pride in our mandate to promote the socially responsible use of legal cannabis. https://lildurk.com/ Previous Comments: ------------------------------------------------------------------------ [2003-08-20 14:22:04] gms08701 at yahoo dot com You can contact me at my email address about testing the patches. Thanks. ------------------------------------------------------------------------ [2003-08-20 13:22:00] kalowsky@php.net yes I know about the cursor issue, and have been working on a solution. Just lost time to work on it. Marking this as closed as it's a symantec thing. For what it's worth I do have the patch that Clara Liu speaks about in the forementioned article on DB2, and would enjoy having others test it. ------------------------------------------------------------------------ [2003-08-17 13:19:44] gms08701 at yahoo dot com 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 ------------------------------------------------------------------------ [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 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 https://bugs.php.net/bug.php?id=25112 -- Edit this bug report at https://bugs.php.net/bug.php?id=25112&edit=1