Re: ByteA for binary data?

From: Robert Myers <ccrider(at)whiterose(dot)net>
To: Doug McNaught <doug(at)wireboard(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: ByteA for binary data?
Date: 2002-02-25 03:39:51
Message-ID: Pine.BSF.4.21.0202242238030.22882-100000@ns1.whiterose.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

My biggest issue with the LO's is that I can't seem to find anything on
how to list _all_ of my LO's.

If I lose the OID, I've got a LO out there with no pointer to it.

Am I missing something on that?

On the 8K limit, I'm not even seeing 8K, I'm seeing about 15 or 16 chars,
not really enough. I'm using the latest PHP, 4.1.1, which didn't work, so
I figured I'd hit 4.2.0 in the CVS tree, no joy there either.

-Bob
ccrider(at)whiterose(dot)net
Systems Administrator for whiterose.net
http://www.whiterose.net

On 24 Feb 2002, Doug McNaught wrote:

> Robert Myers <ccrider(at)whiterose(dot)net> writes:
>
> > I've read the available documentation on LO and bytea, and both seem to
> > have troubles, is this something that will be fixed in a future
> > release? I'm currently running 7.2.
>
> I've been using LOs with great success since 7.1--there are no current
> problems with it, though the API is a little convoluted. I prefer
> them to bytea fields becauser you're not forced to load the whole
> thing into memory either on the server or client side (I work with
> multi-megabyte data files). I use Java on the client.
>
> Have you read the bytea docs on proper quoting? Is your PHP install
> up to date? Older versions would truncate queries at 8k I think...
>
> -Doug
> --
> Let us cross over the river, and rest under the shade of the trees.
> --T. J. Jackson, 1863
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Thomas T. Thai 2002-02-25 03:51:00 Re: ByteA for binary data?
Previous Message Thomas T. Thai 2002-02-25 03:39:50 Re: ByteA for binary data?