Is this issue still open?
Some guys say me that they experience similar troubles and this may
prevent them from migrating from OneBigWellKnownDBMS to Postgres.
On 4/18/06, Eric Mauvière <e.mauviere@xxxxxxxxxx> wrote:
Hello Christopher,
i simply want to retrieve the content of a binary field in a Postgresql
table, and use that information in a PHP script.
That binary field contains binary information that must be read with PHP
binary functions (unpack).
The current way : POSTGRES cursor -> text version of the binary field in
PHP -> conversion back to a binary string with pg_unescape_bytea
is tedious and brings performance issues.
best regards,
Eric Mauvière
----- Original Message -----
From: "Christopher Kings-Lynne" <chris.kings-lynne@xxxxxxxxxxxxxxx>
To: "Eric Mauvière" <e.mauviere@xxxxxxxxxx>
Cc: <pgsql-php@xxxxxxxxxxxxxx>
Sent: Tuesday, April 18, 2006 10:28 AM
Subject: Re: [PHP] binary cursor returning truncated data
>> for that confirmation
>>
>> I reported the bug to the PHP team, and they issued a patch.
>>
>> I would also suggest to postgres developpers to simplify their code and
>> go back to SQL standards :)
>> That BINARY CURSOR thing should be avoided. With MySQL for instance, a
>> cursor will read the same way any type of data, binary or text.
>
> I think you're rather confused. The BINARY CURSOR is for emitted binary
> data, not reading it. If you declare a normal cursor over a binary
> (bytea) field, you will get its text representation quite happily.
>
> Chris
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>
>
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
--
Best regards,
Nikolay
