From: | "Martin A(dot) Marques" <martin(at)math(dot)unl(dot)edu(dot)ar> |
---|---|
To: | Ned Lilly <ned(at)greatbridge(dot)com>, adam(at)newsnipple(dot)com |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PHP - Postgres large object functions |
Date: | 2001-01-25 13:06:16 |
Message-ID: | 01012510061605.07407@math.unl.edu.ar |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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(dot)rethans(at)jdimedia(dot)nl>
> <mailto:d(dot)rethans(at)jdimedia(dot)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(at)newsnipple(dot)com> <mailto:adam(at)newsnipple(dot)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(at)math(dot)unl(dot)edu(dot)ar
Santa Fe - Argentina http://math.unl.edu.ar/~martin/
Administrador de sistemas en math.unl.edu.ar
-----------------------------------------------------------------
From | Date | Subject | |
---|---|---|---|
Next Message | Denis Perchine | 2001-01-25 14:13:09 | Re: (one more time) Patches with vacuum fixes available . |
Previous Message | Frank Joerdens | 2001-01-25 12:35:05 | Re: beta3 Solaris 7 (SPARC) port report [ Was: Looking for . . . ] |