Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 542AC63245F for ; Wed, 25 Aug 2010 21:02:11 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 65008-03 for ; Thu, 26 Aug 2010 00:02:03 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from tempest.mainecoon.com (tempest.mainecoon.com [69.12.217.123]) by mail.postgresql.org (Postfix) with ESMTP id C185F632282 for ; Wed, 25 Aug 2010 21:02:03 -0300 (ADT) Received: from [10.1.1.2] (fw.boscorama.com [75.101.8.88]) by tempest.mainecoon.com (Postfix) with ESMTPSA id 1CFAE6EA0FE for ; Wed, 25 Aug 2010 17:02:01 -0700 (PDT) Message-ID: <4C75AEF8.80605@boscorama.com> Date: Wed, 25 Aug 2010 17:02:00 -0700 From: Bosco Rama User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.1.11) Gecko/20100701 SeaMonkey/2.0.6 MIME-Version: 1.0 To: pgsql-interfaces@postgresql.org Subject: Re: Large object support in ecpg References: <4C5B3878.4000101@boscorama.com> In-Reply-To: <4C5B3878.4000101@boscorama.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-5 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201008/7 X-Sequence-Number: 6935 Hi again, Bosco Rama wrote: > > This is probably an FAQ but is there any direct support of large > objects in ECPG? So from the lack of response I assume not. I certainly couldn't find any reference to large objects in the ecpg docs, web or any forums. The issue I have is that I want to integrate a large object into a transaction started in a function using ecpg. This means I have to use ecpg to perform the large object 'write' (I'd prefer a stream methodology) or 'import'. Either that or I need to grab a reference to the connection used by the ecpg lib and use it in some PQ code. I'm not sure I can do either of those as it stands now. I guess I could also try ecpg against a transaction started in PQ code but that seems even more fraught with danger. And is even less obvious. BTW, we are using 8.4.4 right now. Any words of wisdom from the ecpg cognoscenti? Thanks for any help with this. Bosco.