|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #62215 ODBC: ms access memo field causes cli abend
Submitted: 2012-06-03 14:48 UTC Modified: 2014-01-01 12:37 UTC
Avg. Score:4.6 ± 0.7
Reproduced:8 of 8 (100.0%)
Same Version:2 (25.0%)
Same OS:6 (75.0%)
From: ned at cop dot ufl dot edu Assigned:
Status: Open Package: PDO ODBC
PHP Version: 5.4.3 OS: windows
Private report: No CVE-ID: None
Have you experienced this issue?
Rate the importance of this bug to you:

 [2012-06-03 14:48 UTC] ned at cop dot ufl dot edu
this problem was first noticed with 5.4.1; 5.4.0 works fine.

i am using PDO to read a ms access database with a memo field, at the command line interface. i created a test database with one table and one field of type memo and one record. if the text in that field is 255 chars of less, all is well. between 256 and 259 php returns scrambled data. at 260 it gives "zend mm heap corrupted". at 261 CLI blows up.

Test script:

$dbq = "test.mdb";
$sql = "SELECT * FROM table1";
$pdo = new PDO("odbc:Driver={Microsoft Access Driver (*.mdb)};Dbq=$dbq;");
$result = $pdo->query($sql,PDO::FETCH_ASSOC);
foreach ($result as $row)
   echo $row['COMMENT'] . "\n";


Expected result:
the script should return whatever chars are in the memo field, up to 65536 max. instead it only handles 255 chars as if it were a text field.

Actual result:
between 256 and 259 returns scrambled data. at 260 gives "zend mm heap corrupted". a 261 CLI blows up.


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2013-06-12 04:52 UTC]
-Summary: ms access memo field causes cli abend +Summary: ODBC: ms access memo field causes cli abend
 [2014-01-01 12:37 UTC]
-Package: PDO related +Package: PDO ODBC
PHP Copyright © 2001-2020 The PHP Group
All rights reserved.
Last updated: Thu Jul 09 10:01:25 2020 UTC