Adam, FYI, according to Rasmus Lerdorf, your patches have been 
committed.  From the changelog:

    2001-01-18  Derick Rethans  <d.rethans@jdimedia.nl> <mailto:d.rethans@jdimedia.nl>
    
        * ext/pgsql/pgsql.c
          ext/pgsql/php_pgsql.h:
        - Added the pg_lolseek function, which allows for arbitrary seeking within
          a large object, and the pg_lotell call, which can be used to find the
          current file offset for a large object (Submitted by: Adam Haberlach
          <adam@newsnipple.com> <mailto:adam@newsnipple.com>).
        - Added the pg_lolseek and pg_lotell functions
    

Regards,
Ned

-- 
----------------------------------------------------
Ned Lilly                     e: ned@greatbridge.com
Vice President                w: www.greatbridge.com
Evangelism / Hacker Relations        v: 757.233.5523
Great Bridge, LLC                    f: 757.233.5555



-- Adam's original message:

On Mon, Jan 22, 2001 at 11:55:56PM -0500, Bruce Momjian wrote:
> > On Wed, Dec 27, 2000 at 12:56:26AM -0500, Bruce Momjian wrote:
> > > I have been asked by the major PHP developer Rasmus Lerdorf to see if
> > > the PostgreSQL/PHP interface needs any improvements.
> > > 
> > > Is the current PostgreSQL interface module in PHP adequate?  Does it
> > > support all the current libpq features?
> > > 
> > > If not, would someone submit some patches to the PHP folks.  They want
> > > us to work well with PHP.  They are basically encouraging us to improve
> > > it in any way we can.
> > 
> > 	I use PHP and Postgres together quite a bit, and find the APIs
> > complete enough for most things.  However, just last week I implemented
> > 
> > pg_lolseek($loid, $offset $whence)
> > and
> > pg_lotell($loid)
> > 
> > For some stuff that we are working on.  They are pretty straightforward,
> > and I can package them up and submit them if someone wants.
> > 

> Would to send this over to the PHP folks for inclusion?  Thanks.

	I sent them patches against the at-the-time up-to-date CVS tree back
when this first came up, they said that they failed, so I sent them another
set, and have not heard back from them.  It doesn't seem to show up in the
cvs logs.

	I'll bug someone again and see if I can find out what happened.  I mean,
they only have 240 people with write access to the cvs tree...

-- 
Adam Haberlach            |A cat spends her life conflicted between a
adam@newsnipple.com       |deep, passionate, and profound desire for
http://www.newsnipple.com |fish and an equally deep, passionate, and
'88 EX500                 |profound desire to avoid getting wet.



Wed, 24 Jan 2001 14:56:26 -0600
Ned Lilly <ned@greatbridge.com>
PHP - Postgres large object functions
El Miï¿½ 24 Ene 2001 17:56, Ned Lilly escribiï¿½:
> Adam, FYI, according to Rasmus Lerdorf, your patches have been
> committed.  From the changelog:
>
>     2001-01-18  Derick Rethans  <d.rethans@jdimedia.nl>
> <mailto:d.rethans@jdimedia.nl>
>
>         * ext/pgsql/pgsql.c
>           ext/pgsql/php_pgsql.h:
>         - Added the pg_lolseek function, which allows for arbitrary seeking
> within a large object, and the pg_lotell call, which can be used to find
> the current file offset for a large object (Submitted by: Adam Haberlach
> <adam@newsnipple.com> <mailto:adam@newsnipple.com>).
>         - Added the pg_lolseek and pg_lotell functions

I've had headaches trying to understand how PHP works with postgres large 
objects. Is there some kind of "understandable" docs on this behave?

Saludos... :-)

-- 
System Administration: It's a dirty job, 
but someone told I had to do it.
-----------------------------------------------------------------
Martï¿½n Marquï¿½s			email: 	martin@math.unl.edu.ar
Santa Fe - Argentina		http://math.unl.edu.ar/~martin/
Administrador de sistemas en math.unl.edu.ar
-----------------------------------------------------------------

Thu, 25 Jan 2001 10:06:16 -0300
"Martin A. Marques" <martin@math.unl.edu.ar>
Re: PHP - Postgres large object functions