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: schnettker 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 OCI Operating System: Linux - Fedora Core 1 PHP Version: 5.1.0RC3 Assigned To: wez Block user comment: N Private report: N New Comment: Thanks Wilbert. You made my "decade". After many years i found a good solution. varchar2(300) works as a workaround for us Previous Comments: ------------------------------------------------------------------------ [2017-03-04 03:34:19] slavkoss22 at gmail dot com I have same problem with varchar2(100). I think we should use E.Rangel's PDOOCI syntax on oci8 driver until PHP PDO extension will be fixed (ever or never). ------------------------------------------------------------------------ [2015-01-30 15:38:36] glueck at ibou dot net I fix this problem by this way: connectionstring: "oci:dbname={$tns};charset=UTF8" Know the driver will handel UTF8 inside a field correct. ------------------------------------------------------------------------ [2013-03-12 19:05:02] wilbert dot j at gmail dot com We found a "solution" to get it work: select cast( tbl.description AS varchar2(300) )as desc FROM database.table tbl; ------------------------------------------------------------------------ [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 ------------------------------------------------------------------------ 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