#37100 [Asn->Csd]: data is returned truncated with BINARY CURSOR
| From: | felipe@php.net | Date: | Mon, 13 Oct 2008 13:45:41 +0000 |
| Subject: | #37100 [Asn->Csd]: data is returned truncated with BINARY CURSOR | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-129665@lists.php.net to get a copy of this message | ||
ID: 37100
Updated by: felipe@php.net
Reported By: e dot mauviere at geoclip dot fr
-Status: Assigned
+Status: Closed
Bug Type: PostgreSQL related
Operating System: WIN XP PRO
PHP Version: 5.1.2
Assigned To: helly
New Comment:
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.
Fixed in 5.2.7, 5.3 and HEAD.
Previous Comments:
------------------------------------------------------------------------
[2008-01-22 15:31:14] maciej dot pijanka at gmail dot com
Same problem happens with postgresql 8.2.5, php 5.2.5 on linux
$ php.cli test-37100.php
\001\003\252\000\010\022
0103aa000812
3
0103aa
i only added to test case printing newlines to get more readable
output.
------------------------------------------------------------------------
[2006-05-20 18:34:07] e dot mauviere at geoclip dot fr
sorry to insist, but if there is a patch now, i would be very glad to
benefit from it...
------------------------------------------------------------------------
[2006-04-16 22:17:19] tony2001@php.net
Marcus, please test the patch:
http://tony2001.phpclub.net/dev/tmp/bug37100.diff
I don't have/use PG, so unfortunately I can't do it myself.
------------------------------------------------------------------------
[2006-04-16 20:32:21] e dot mauviere at geoclip dot fr
Description:
------------
Impossible to retrieve properly binary data from a binary field in
Postgresql.
It should work with the SQL BINARY CURSOR OPTION in Postgres, but data
returned is truncated.
Reproduce code:
---------------
CREATE TABLE test(binfield byteA) ;
INSERT INTO test VALUES (decode('0103AA000812','hex'));
//First try
$data =pg_query("SELECT binfield FROM test");
$res=pg_fetch_result($data,0);
echo $res; // =>"\001\003\252\000\010\022"
echo bin2hex(pg_unescape_bytea($res)); //=> "0103aa000812"
//By default, Potsgresql returns binary field values as strings, so we
need to unescape them to restore original binary data. Tedious.
Performance issue here.
//second try
$sql="BEGIN;DECLARE mycursor BINARY CURSOR FOR SELECT binfield FROM
test;fetch all in mycursor;";
//the BINARY CURSOR option forces PostgreSQ to return binary data
$data =pg_query($sql);
$res=pg_fetch_result($data,0);
echo strlen($res); //=> 3
echo bin2hex($res); //=> 0103aa
//BUG : data returned is truncated, as soon as a "00" byte is
encountered,
Expected result:
----------------
i am expecting to retrieve full binary content
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=37100&edit=1