Bug #35003 [Com]: Warning: PDOStatement::fetch(): column 0 data was too large for buffer and was

Edit report at https://bugs.php.net/bug.php?id=35003&edit=1 ID: 35003 Comment by: wilbert dot j at gmail dot com Reported by: derick@php.net Summary: Warning: PDOStatement::fetch(): column 0 data was too large for buffer and was Status: Closed Type: Bug Package: PDO related Operating System: Linux - Fedora Core 1 PHP Version: 5.1.0RC3 Assigned To: wez Block user comment: N Private report: N New Comment: We found a "solution" to get it work: select cast( tbl.description AS varchar2(300) )as desc FROM database.table tbl; Previous Comments: ------------------------------------------------------------------------ [2012-08-31 14:20:03] mouder at mail dot bg Still happens to me with PDO and Oracle. ------------------------------------------------------------------------ [2012-03-06 17:52:59] lucassouza1 at gmail dot com This issue still happens. I suppose it occurs because for example, an oracle varchar(10) column, is filled with a multibyte char sequence like "maçã", it will overflow the buffer if a charset like 'AL32UTF8' is provided in DSN ------------------------------------------------------------------------ [2011-11-04 15:53:21] tomasz at trejderowski dot pl Sorry, not true. As reported in many similar bug reports (in year 2005 and 2007) and comments to them (in year 2007, 2010 and 2011) this issue is STILL NOT FIXED. Up until end of 2011. At least not for PHP + PDO + Oracle. ------------------------------------------------------------------------ [2005-10-28 17:02:53] tony2001@php.net This bug has been fixed in CVS. Snapshots of the sources are packaged every three hours; this change will be in the next snapshot. You can grab the snapshot at http://snaps.php.net/. Thank you for the report, and for helping us make PHP better. ------------------------------------------------------------------------ [2005-10-27 18:59:24] vs at ez dot no Note that the query result is wrong. There actually should have been 0 instead of "". This is probably caused by the same problem. ------------------------------------------------------------------------ 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=35003 -- Edit this bug report at https://bugs.php.net/bug.php?id=35003&edit=1