#18744 [Fbk->NoF]: blob_add has max limit of 64k

ID: 18744 Updated by: php-bugs@lists.php.net Reported By: cheald45@hotmail.com -Status: Feedback +Status: No Feedback Bug Type: InterBase related Operating System: Redhat 7.3 PHP Version: 4.2.2 New Comment: No feedback was provided for this bug for over 2 weeks, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open". Previous Comments: ------------------------------------------------------------------------ [2002-12-04 22:52:20] sniper@php.net Please try using this CVS snapshot: http://snaps.php.net/php4-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-latest.zip ------------------------------------------------------------------------ [2002-08-05 14:42:22] cheald45@hotmail.com The ibase_blob_add functionality wraps the Interbase blob add functionality, which will only allow up to 64k of data to be added at any one time dut to an unsigned short variable. This means that if a chunk of data is > than 64k, you have to split it into < 64k chunks and run multiple adds. While this is not a problem, it seems that this functionality would be better used in the actual PHP source. It shouldn't be too hard a fix - just split the incoming string into < 64k chunks and run the add in a loop. For example, we discovered that a 145k string was being truncated by the ibase_blob_add function. At the very least, the ibase_blob_add function should throw a warning if the data is > 64k. This 64k limit is not documented, and has been a source of much confusion. It would be very helpful if this change were implemented. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=18744&edit=1