Received: from james.webteknics.com (65-85-235-195.client.dsl.net
	[65.85.235.195])
	by postgresql.org (Postfix) with ESMTP id 7A35C47594B
	for <pgsql-interfaces@postgresql.org>;
	Wed, 17 Jul 2002 13:35:00 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by james.webteknics.com (8.11.6/8.11.6) id g6HHbHK02661;
	Wed, 17 Jul 2002 13:37:17 -0400
Content-Type: text/plain;
  charset="iso-8859-1"
From: James Orr <james@lrgmail.com>
To: Jeremy Buchmann <jeremy@wellsgaming.com>
Subject: Re: bytea on windows perl client
Date: Wed, 17 Jul 2002 13:37:16 -0400
User-Agent: KMail/1.4.1
Cc: pgsql-interfaces@postgresql.org
References: <2249A4CB-99A9-11D6-BECC-000502E740BA@wellsgaming.com>
In-Reply-To: <2249A4CB-99A9-11D6-BECC-000502E740BA@wellsgaming.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200207171337.16475.james@lrgmail.com>
X-Archive-Number: 200207/104
X-Sequence-Number: 2913

On Wednesday 17 July 2002 01:17 pm, Jeremy Buchmann wrote:
> >> \211PNG\015\012\000 and so on.
> >
> > This is the escaped output form of bytea. It seems that on linux the
> > perl script is either using a binary cursor, or automagically
> > unescaping the output, while on windows it isn't. I'm not sure why that
> > would happen, but hopefully one of the perl gurus hanging around will
> > chime in.
> >
> > Joe
>
> James,
>
> This may be a long shot, but try to binmode your output stream:
>
> Let us know how it works.

I did this ...

print "Content-type: image/png\n\n";
binmode STDOUT;
print $image;

Didn't work.

- James