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 04:35:24 |
Message-ID: | Pine.BSF.4.21.0202242334530.29322-100000@ns1.whiterose.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Yes, this is helpful.
This _really_ should be in the docs somewhere, I read and read, and
thought I had some of it figured out, but I didn't. :)
Thanks again.
-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:
>
> > 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.
>
> SELECT DISTINCT loid FROM pg_largeobject;
>
> > If I lose the OID, I've got a LO out there with no pointer to it.
>
> There's a utility in contrib/ called vacuum_lo that can help with
> that. You can also put a trigger on your referring table to make sure
> LOs get deleted (that's what I do).
>
> > Am I missing something on that?
>
> As I said, the API is a little convoluted, but it's not hard to use
> and works well.
>
> > 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.
>
> I'm guessing you're not quoting the bytea strings properly, but I've
> not used PHP or bytea myself so I can't really help.
>
> -Doug
> --
> Let us cross over the river, and rest under the shade of the trees.
> --T. J. Jackson, 1863
>
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Myers | 2002-02-25 04:36:20 | Re: ByteA for binary data? |
Previous Message | Doug McNaught | 2002-02-25 04:25:41 | Re: ByteA for binary data? |