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).
pg_lo_write
(PHP 4 >= 4.2.0, PHP 5, PHP 7, PHP 8)
pg_lo_write — Scrive un large object
Descrizione
pg_lo_write() scrive su un large object
i dati della variabile dati e restituisce il numero
di byte scritti, oppure false in caso di errore.
large_object รจ una risorsa large object ottenuta
attraverso pg_lo_open().
Per utilizzare l'interfaccia large object (lo), occorre includere il comando in un blocco di transazione.
Nota:
Questa funzione si chiamava
pg_lo_write().
Vedere anche pg_lo_create() e pg_lo_open().
add a note
User Contributed Notes 2 notes
cedric at isoca.com ¶
23 years ago
nandrews at logictree dot co dot uk ¶
21 years ago
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.
