From: Christopher Kings-Lynne <chris.kings-lynne@calorieking.com>
To: Eric Mauvière <e.mauviere@geoclip.fr>
Cc: pgsql-php@postgresql.org
Subject: Re: binary cursor returning truncated data
Date: Tue, 18 Apr 2006 16:28:20 +0800
Message-ID: <4444A324.20904@calorieking.com> (raw)
In-Reply-To: <015501c662be$419d6460$0200a8c0@EMC3>
References: <020401c65e3c$70721050$0200a8c0@EMC3>
<20060416163932.GA30082@winnie.fuhr.org>
<015501c662be$419d6460$0200a8c0@EMC3>
> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-php@postgresql.org
Cc: chris.kings-lynne@calorieking.com, e.mauviere@geoclip.fr
Subject: Re: binary cursor returning truncated data
In-Reply-To: <4444A324.20904@calorieking.com>
References: <020401c65e3c$70721050$0200a8c0@EMC3> <20060416163932.GA30082@winnie.fuhr.org> <015501c662be$419d6460$0200a8c0@EMC3> <4444A324.20904@calorieking.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox