Skip site navigation (1) Skip section navigation (2)

PHP - Postgres large object functions

From: Ned Lilly <ned(at)greatbridge(dot)com>
To: adam(at)newsnipple(dot)com
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: PHP - Postgres large object functions
Date: 2001-01-24 20:56:26
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Adam, FYI, according to Rasmus Lerdorf, your patches have been 
committed.  From the changelog:

    2001-01-18  Derick Rethans  <d(dot)rethans(at)jdimedia(dot)nl> <mailto:d(dot)rethans(at)jdimedia(dot)nl>
        * ext/pgsql/pgsql.c
        - 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(at)newsnipple(dot)com> <mailto:adam(at)newsnipple(dot)com>).
        - Added the pg_lolseek and pg_lotell functions


Ned Lilly                     e: ned(at)greatbridge(dot)com
Vice President                w:
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(at)newsnipple(dot)com       |deep, passionate, and profound desire for |fish and an equally deep, passionate, and
'88 EX500                 |profound desire to avoid getting wet.


pgsql-hackers by date

Next:From: Lamar OwenDate: 2001-01-24 21:06:38
Subject: Re: postgresql.conf and postgres options
Previous:From: Frank JoerdensDate: 2001-01-24 20:55:31
Subject: beta3 Solaris 7 (SPARC) port report [ Was: Looking for . . . ]

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group