#17719 [Fbk->NoF]: Code Garbage in Longtext results

ID: 17719 Updated by: kalowsky@php.net Reported By: php@remove.gustl.net -Status: Feedback +Status: No Feedback Bug Type: ODBC related Operating System: W98,W2K PHP Version: 4.2.1 New Comment: No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to "Open". Thank you. Previous Comments: ------------------------------------------------------------------------ [2002-06-24 18:54:15] paul@distributed.net 4.1.2 seems to provide the correct output from the page. current cvs version seems to corrupt output. dank, i could probably give you remote access or get a debugger loaded on it tomorrow. Paul ------------------------------------------------------------------------ [2002-06-24 17:43:50] kalowsky@php.net Please realize that while database A may support functionality MNOP, ODBC functionality is NOT assured. To answer the question, no I do not use an MS database. My testing comes from using iODBC and unixODBC ODBC drivers, and Virtuoso and PostgreSQL-ODBC for functionality. ------------------------------------------------------------------------ [2002-06-24 17:31:53] php@remove.gustl.net do you use a mssql database? then you can create the table with the mssql enterprise manager, or a can open you a mssql test access on my server, Gustav Graf ------------------------------------------------------------------------ [2002-06-24 17:16:32] kalowsky@php.net Unfortunately I cannot test this. My local database dies upon trying to create a table with type NTEXT via ODBC. ------------------------------------------------------------------------ [2002-06-24 17:10:41] php@remove.gustl.net No, I cannot change the table definitions, because they are parts of an existing application. I was very happy to find out the "SET TEXTSIZE" trick, do get access to the NTEXT columns, without that PHP was and is still crashing. But something must have changed from PHP version 4.1.1 to 4.2.1, that this is not working any more. Reminds me a littlebit on that error I had with an WinXP Apache 1.3.19 installation, where I got simmilar code garbage in html results, I found a patch for apache to fix that, maybe that helps Gustav Graf ------------------------------------------------------------------------ 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/17719 -- Edit this bug report at http://bugs.php.net/?id=17719&edit=1