Message-ID: <4C76A426.4050904@boscorama.com>
Date: Thu, 26 Aug 2010 10:28:06 -0700
From: Bosco Rama <postgres@boscorama.com>
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> <4C75AEF8.80605@boscorama.com>
	<4C765D4F.4010606@gmail.com>
In-Reply-To: <4C765D4F.4010606@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Satoshi Nagayasu wrote:
> 
> 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 for this.  I wonder why a google search didn't find this?
Anyway, that describes pretty much what I figured I'd have to do.

However, I would really like a sanctioned method.  It seems that
using the above function is not deemed 'proper'.  But if this is
the only way to do it, then I guess I'll need to be a bad boy. :-)

Thanks again.

Bosco.