X-Original-To: pgsql-php-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id AA10911F602E for ; Tue, 18 Apr 2006 05:28:13 -0300 (ADT) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Score: 0.224 X-Spam-Level: X-Spam-Status: No, score=0.224 required=5 tests=[AWL=0.224] Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 1Qi-iUPb3h+l for ; Tue, 18 Apr 2006 05:28:09 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from houston.familyhealth.com.au (houston.au.fhnetwork.com [203.22.197.21]) by postgresql.org (Postfix) with ESMTP id B1F1E11F6C96 for ; Tue, 18 Apr 2006 05:28:09 -0300 (ADT) Received: from houston.familyhealth.com.au (localhost [127.0.0.1]) by houston.familyhealth.com.au (Postfix) with ESMTP id 347292542F; Tue, 18 Apr 2006 16:28:05 +0800 (WST) Received: from [127.0.0.1] (work-40.internal [192.168.0.40]) by houston.familyhealth.com.au (Postfix) with ESMTP id 3FC47253E9; Tue, 18 Apr 2006 16:28:03 +0800 (WST) Message-ID: <4444A324.20904@calorieking.com> Date: Tue, 18 Apr 2006 16:28:20 +0800 From: Christopher Kings-Lynne User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: =?ISO-8859-1?Q?Eric_Mauvi=E8re?= Cc: pgsql-php@postgresql.org Subject: Re: binary cursor returning truncated data References: <020401c65e3c$70721050$0200a8c0@EMC3> <20060416163932.GA30082@winnie.fuhr.org> <015501c662be$419d6460$0200a8c0@EMC3> In-Reply-To: <015501c662be$419d6460$0200a8c0@EMC3> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-familyhealth-MailScanner-Information: Please contact the ISP for more information X-familyhealth-MailScanner: Found to be clean X-familyhealth-MailScanner-From: chris.kings-lynne@calorieking.com X-Archive-Number: 200604/12 X-Sequence-Number: 3482 > 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