Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 3729F6326F1 for ; Thu, 26 Aug 2010 09:26:11 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 25196-01 for ; Thu, 26 Aug 2010 12:26:02 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-pv0-f174.google.com (mail-pv0-f174.google.com [74.125.83.174]) by mail.postgresql.org (Postfix) with ESMTP id CE0A96326CF for ; Thu, 26 Aug 2010 09:26:03 -0300 (ADT) Received: by pvg2 with SMTP id 2so604142pvg.19 for ; Thu, 26 Aug 2010 05:26:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=2UzLTLM7XFojRqEZLnFLVfVQHBY8D7piuP6YDGFDPmo=; b=vuphKRR8dD+mxlJMyFUKmrSpEOc7slDkTPkiHB4+chUFz1JllqLMINSduuXnJNLph/ 0tD5yAwP9z73+yMbAXLSfTobSt6op/DZKfHVh3CYmY7zkepzToXJ2EGaYSB6WcW9cCIh 9aBBEGruqLTus6t1VphVBvHCqyTMGv3cb8Mzw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=bm3D9RfspRcErPBCTkZw58HHOI0u+4JhxLSYd8J8pF+rrlJ6Q31ZlaIL27d/poc3xW 9zHmYYb5dwgPd7dYfilbjjCuhSe6iwvrLg7WGJ99se7KzAJ3zY6MlnHLLQeeFwFDj9Ej c1uMV2nq+QK7kMohaRCbMzRbcG8E1SAZaWfIg= Received: by 10.142.218.14 with SMTP id q14mr8276093wfg.89.1282825561878; Thu, 26 Aug 2010 05:26:01 -0700 (PDT) Received: from [10.0.2.101] (p0245ed.tokyff01.ap.so-net.ne.jp [121.2.69.237]) by mx.google.com with ESMTPS id 23sm2906763wfa.22.2010.08.26.05.25.58 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 26 Aug 2010 05:25:59 -0700 (PDT) Message-ID: <4C765D4F.4010606@gmail.com> Date: Thu, 26 Aug 2010 21:25:51 +0900 From: Satoshi Nagayasu User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2 MIME-Version: 1.0 To: Bosco Rama CC: pgsql-interfaces@postgresql.org Subject: Re: Large object support in ecpg References: <4C5B3878.4000101@boscorama.com> <4C75AEF8.80605@boscorama.com> In-Reply-To: <4C75AEF8.80605@boscorama.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201008/8 X-Sequence-Number: 6936 Hi Bosco, On 2010/08/26 9:02, Bosco Rama wrote: > 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. I had some experiences on using large objects in ECPG with using ECPGget_PGconn(). However, ECPGget_PGconn() is not recommended in ECPG application, so it's "at your own risk". For more details, please download my document from below, and check "Large Objects" section to handle large objects. http://code.google.com/p/ecpgdocs/downloads/detail?name=ecpg_html.zip&can=2&q=#makechanges Thanks, -- NAGAYASU Satoshi