pg_lo_unlink
Using php 4.3.0 and PostgreSQL 7.3.1
I can write a simple script in which pg_lo_write seems to always return 1 and not the number of bytes written, as evidenced by extracting the data through another means.
Further more, I can make this pg_lo_write fail, or at least fail to write all the data it's pretty difficult to tell without the number of bytes written being returned, and not return the false value. In addition to this, the lo resource has been adjusted so that the oid it contains is 0.
Unfortunately, I do not know what exactly the failure mode is, it does seem to be in the ip network communication side of PostgreSQL, which is odd since the unix domain comms works fine for this. However, it would have been useful to have the pg_lo_write() function return as advertised, it would have saved some of the 2 man hours me and the dev. team put into diagnosing this problem.
pg_lo_write
(PHP 4 >= 4.2.0, PHP 5)
pg_lo_write — Zapisuje do wielkiego obiektu (Large Object - LO)
Opis
int pg_lo_write
( resource $large_object
, string $data
)
pg_lo_write() zapisuje jak najwięcej do wielkiego obiektu ze zmiennej data i zwraca liczbę bajtów zapisanych, lub FALSE jeśli wystąpił błąd. Paramter large_object jest identyfikatorem polączenia z pg_lo_open().
Użycie interfejsu wielkich obiektów (LO) wymaga zamknięcia wszystkich operacji z nim związanych wewnątrz transakcji.
Informacja: Ta funkcja była poprzednio nazwana pg_lowrite().
Zobacz także pg_lo_create() i pg_lo_open().
add a note
User Contributed Notespg_lo_write
nandrews at logictree dot co dot uk
05-Jun-2003 05:17
05-Jun-2003 05:17
cedric at isoca.com
27-Apr-2001 02:26
27-Apr-2001 02:26
Be aware when you modify a lo with pg_lowrite() to remove first the old one : if the new lo is smaller than the one before, it only overwrite the begining and you keep the end of the old lo (open with "w" parameter, PHP 4.04 Linux RH).