The problem is isolated to PDO ODBC -- old school ODBC works fine.
Below are my test cases.
Plain old ODBC:
$stp = 'SELECT attdata FROM fm_faxin_att WHERE id = 11908591344 AND
attid = 0'; // statement to prepare
$ps = odbc_prepare($res, $stp);
if (!$res) { die ('failed to prepare stateme
On Wednesday 26 September 2007, Carlton Whitehead wrote:
> Could this be some bug in the way PHP, PDO, ODBC, and/or MS SQL are
> communicating? Maybe 'image' columns aren't being handled correctly?
> I'm fairly certain my code is correct. I appreciate all of your comments.
>
> Has anyone even tr
No, the faxes aren't 4GB. Most of the faxes are less than 50KB,
although they can be as large as a few MB. 4GB is a ridiculous amount
of memory to try to allocate for this. 4GB is the max that 32bit
versions of Windows can see. Is something causing the memory allocation
to loop until it rea
On Thursday 27 September 2007 04:21, Carlton Whitehead wrote:
> Hi everyone,
>
> I'm working on a script that downloads archived fax images (TIFFs and PDFs)
> from a MS SQL Server using the PDO ODBC driver. I get the below error
> regardless of which fax I try to get from the database. Each fax is
Hi everyone,
I'm working on a script that downloads archived fax images (TIFFs and PDFs)
from a MS SQL Server using the PDO ODBC driver. I get the below error
regardless of which fax I try to get from the database. Each fax is a different
size, and both of the memory allocation numbers are alw
5 matches
Mail list logo