X-Original-To: pgsql-interfaces-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 5E704D8BB1 for ; Fri, 23 Sep 2005 07:52:42 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 25364-09 for ; Fri, 23 Sep 2005 10:52:36 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.177]) by svr1.postgresql.org (Postfix) with ESMTP id 3B7E4D8134 for ; Fri, 23 Sep 2005 07:52:37 -0300 (ADT) Received: from p508954A1.dip.t-dialin.net [80.137.84.161] (helo=feivel) by mrelayeu.kundenserver.de with ESMTP (Nemesis), id 0MKwh2-1EIlAR0gSv-0006Wr; Fri, 23 Sep 2005 12:52:35 +0200 Received: by feivel (Postfix, from userid 1000) id 835A64B014; Fri, 23 Sep 2005 12:52:32 +0200 (CEST) Date: Fri, 23 Sep 2005 12:52:32 +0200 From: Michael Meskes To: Michael Fuhr Cc: Mark Richardson , pgsql-interfaces@postgresql.org Subject: Re: libpq, ecpg and the bytea data type Message-ID: <20050923105232.GA28941@1> Mail-Followup-To: Michael Fuhr , Mark Richardson , pgsql-interfaces@postgresql.org References: <20050915191806.66041.qmail@unknown-206-190-38-164.yahoo.com> <20050916002222.GA72513@winnie.fuhr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050916002222.GA72513@winnie.fuhr.org> User-Agent: Mutt/1.5.10i X-Provags-ID: kundenserver.de abuse@kundenserver.de login:da5cff6069dd6897c77170232368d0ba X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.042 required=5 tests=[AWL=0.042] X-Spam-Level: X-Archive-Number: 200509/37 X-Sequence-Number: 5760 On Thu, Sep 15, 2005 at 06:22:22PM -0600, Michael Fuhr wrote: > In any case, others have reported trouble handling bytea with ECPG; > see the list archives for previous discussion. I see a lot of calls > to strlen() in the ECPG source code, so it might not be designed > to handle binary data. You might need to fetch the data in non-binary Your right, it is not. ECPG at the moment expects data to be ascii and translates it into the type of the variable. Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes@jabber.org Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!