Re: [GENERAL] different results for large objects

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: c k <shreeseva(dot)learning(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org, pgsql-admin(at)postgresql(dot)org
Subject: Re: [GENERAL] different results for large objects
Date: 2009-03-17 12:43:05
Message-ID: 6995.1237293785@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-general

c k <shreeseva(dot)learning(at)gmail(dot)com> writes:
> I am getting correct results with following query i.e. binary objects as
> they are inserted.

> select docimages.* from docimages where docimages.accobjecttype=9 ORDER BY
> docimages.docimagename;

> but when I created a function as follows, binary objects are not shown,

There is no server-side behavior that would cause that query to show you
a large object's contents instead of its identifying number. I suppose
that you have some client-side code that does something magic when it
sees a result column of type "lo", and that for some reason this code
is not successfully recognizing the case where the column is coming out
of a function. Since you've shown us neither the troublesome query
nor the client-side code, it's hard to speculate further than that.

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Alvaro Herrera 2009-03-17 13:18:50 Re: Need help to restore database
Previous Message c k 2009-03-17 11:56:44 different results for large objects

Browse pgsql-general by date

  From Date Subject
Next Message Daniel Verite 2009-03-17 12:48:18 Re: Escaping special characters
Previous Message Thom Brown 2009-03-17 12:39:50 Re: Escaping special characters