X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org
Received: from localhost (av.hub.org [200.46.204.144])
	by postgresql.org (Postfix) with ESMTP id CE57E9DC8AA
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Wed, 14 Dec 2005 03:04:02 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 77593-08
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Wed, 14 Dec 2005 03:04:02 -0400 (AST)
X-Greylist: delayed 03:07:39.804402 by SQLgrey-
Received: from svr2.postgresql.org (svr2.postgresql.org [65.19.161.25])
	by postgresql.org (Postfix) with ESMTP id 3F7179DC84D
	for <pgsql-sql@postgresql.org>; Wed, 14 Dec 2005 03:03:59 -0400 (AST)
Received: from mail.nsasia.co.th (mail.nsasia.co.th [203.146.6.34])
	by svr2.postgresql.org (Postfix) with ESMTP id 59ED4F0B42
	for <pgsql-sql@postgresql.org>; Wed, 14 Dec 2005 03:56:26 +0000 (GMT)
Received: from [192.168.200.39] (helo=mail.nsasia.co.th)
	by astaro.nsasia.co.th with esmtp (Exim 4.43) id 1EmNkW-0005Oa-Pf
	for pgsql-sql@postgresql.org; Wed, 14 Dec 2005 10:56:18 +0700
Received: from Thailand-MTA by mail.nsasia.co.th
	with Novell_GroupWise; Wed, 14 Dec 2005 10:56:07 +0700
Message-Id: <439FFA3F.C5F7.004C.0@nsasia.co.th>
X-Mailer: Novell GroupWise Internet Agent 7.0 
Date: Wed, 14 Dec 2005 10:56:01 +0700
From: "Premsun Choltanwanich" <Premsun@nsasia.co.th>
To: "Tom Lane" <tgl@sss.pgh.pa.us>
Cc: <pgsql-sql@postgresql.org>
Subject: Re: lo function changed in PostgreSQL 8.1.1
References: 
 <439EEEC9.C5F7.004C.0@nsasia.co.th><439EEEC9.C5F7.004C.0@nsasia.co.th>
	<6592.1134488351@sss.pgh.pa.us>
In-Reply-To: <6592.1134488351@sss.pgh.pa.us>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__PartE2C033C1.0__="
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, score=0.001 required=5 tests=[HTML_MESSAGE=0.001]
X-Spam-Score: 0.001
X-Spam-Level: 
X-Archive-Number: 200512/109
X-Sequence-Number: 23651

This is a MIME message. If you are reading this text, you may want to 
consider changing to a mail reader or gateway that understands how to 
properly handle MIME multipart messages.

--=__PartE2C033C1.0__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Dear Tom,
=20
I'm not sure that I understand your word correctly.   But I will explain =
more information
=20
I just need to keep my member's picture into database for showing and may =
have update sometime. I code my program with VB6. I found some suggestion =
to manage lo about lo_in and lo_out that why.
=20
What thing I need to do for continue using lo on PostgreSQL 8.1.1
=20
Ragards,
=20
Premsun

>>> Tom Lane <tgl@sss.pgh.pa.us> 12/13/2005 22:39:11 >>>
"Premsun Choltanwanich" <Premsun@nsasia.co.th> writes:
> lo (Large Object) function that normally shown in function list now =3D
> disappear.  I'm sure that I already check on Large Object box  when I =
=3D
> install. I found some information on http://www.postgresql.org/docs/8.1/i=
nt=3D
> eractive/lo-interfaces.html#AEN26978 about lo function. PostgreSQL has =
=3D
> many new lo function that I never use in version 8.0.4 and some function =
I =3D
> have use is not found (lo_in , lo_out).

lo_in/lo_out aren't needed anymore because lo isn't a separate type,
just a domain over OID.  Why were you using them directly, anyway?

regards, tom lane


--=__PartE2C033C1.0__=
Content-Type: text/html; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Content-Description: HTML

<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dwindows-874=
">
<META content=3D"MSHTML 6.00.2900.2604" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Microsoft Sans Serif">
<DIV>Dear Tom,</DIV>
<DIV>&nbsp;</DIV>
<DIV>I'm not sure that I understand your word correctly.&nbsp;&nbsp; But I =
will explain more information</DIV>
<DIV>&nbsp;</DIV>
<DIV>I just need to keep my member's picture into database for showing&nbsp=
;and may have update sometime. I code my program with VB6. I found some =
suggestion to manage lo about lo_in&nbsp;and lo_out that why.</DIV>
<DIV>&nbsp;</DIV>
<DIV>What thing I need to do for continue using lo on PostgreSQL 8.1.1</DIV=
>
<DIV>&nbsp;</DIV>
<DIV>Ragards,</DIV>
<DIV>&nbsp;</DIV>
<DIV>Premsun</DIV>
<DIV><BR>&gt;&gt;&gt; Tom Lane &lt;tgl@sss.pgh.pa.us&gt; 12/13/2005 =
22:39:11 &gt;&gt;&gt;<BR>"Premsun Choltanwanich" &lt;Premsun@nsasia.co.th&g=
t; writes:<BR>&gt; lo (Large Object) function that normally shown in =
function list now =3D<BR>&gt; disappear.&nbsp; I'm sure that I already =
check on Large Object box&nbsp; when I =3D<BR>&gt; install. I found some =
information on http://www.postgresql.org/docs/8.1/int=3D<BR>&gt; eractive/l=
o-interfaces.html#AEN26978 about lo function. PostgreSQL has =3D<BR>&gt; =
many new lo function that I never use in version 8.0.4 and some function I =
=3D<BR>&gt; have use is not found (lo_in , lo_out).<BR><BR>lo_in/lo_out =
aren't needed anymore because lo isn't a separate type,<BR>just a domain =
over OID.&nbsp; Why were you using them directly, anyway?<BR><BR>regards, =
tom lane<BR></DIV></BODY></HTML>

--=__PartE2C033C1.0__=--