X-Original-To: pgsql-interfaces@postgresql.org
Received: from joeconway.com (66-146-172-86.skyriver.net [66.146.172.86])
	by postgresql.org (Postfix) with ESMTP id 85F30474E4F
	for <pgsql-interfaces@postgresql.org>;
	Thu, 20 Mar 2003 16:52:05 -0500 (EST)
Received: from [206.19.64.3] (account jconway HELO joeconway.com)
	by joeconway.com (CommuniGate Pro SMTP 4.0.4)
	with ESMTP-TLS id 1670208; Thu, 20 Mar 2003 14:28:20 -0800
Message-ID: <3E7A3776.4080302@joeconway.com>
Date: Thu, 20 Mar 2003 13:49:42 -0800
From: Joe Conway <mail@joeconway.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.2.1) Gecko/20021130
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Nigel J. Andrews" <nandrews@investsystems.co.uk>
Cc: =?ISO-8859-1?Q?St=E9phane_Pinel?= <spinel@noos.fr>,
	PostgreSQL-interfaces <pgsql-interfaces@postgresql.org>
Subject: Re: Handling Blobs with libpq
References: <Pine.LNX.4.21.0303202135500.10910-100000@ponder.fairway2k.co.uk>
In-Reply-To: <Pine.LNX.4.21.0303202135500.10910-100000@ponder.fairway2k.co.uk>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Archive-Number: 200303/108
X-Sequence-Number: 3857

Nigel J. Andrews wrote:
> Also, someone recently pointed out that even with bytea if the client encoding
> is different when selecting than it was when storing there is still a chance
> that your data will be come out different to how it should.
> 

If you are using libpq in your own C program, one way around these 
issues (for retrieval anyway) is to use a binary cursor.

Joe