its not very clear if pg_lo_import needs to have pg_lo_open called first. Because pg_lo_import handles the process of writign to the file, it seems logical that pg_lo_open does not need to be called. However due to the ugly nature of how postgres handles oid objects, it would be nice to have this documented.
(PHP 4 >= 4.2.0, PHP 5)
pg_lo_import — Import a large object from file
pg_lo_import() creates a new large object in the database using a file on the filesystem as its data source.
To use the large object interface, it is necessary to enclose it within a transaction block.
Nota: Cuando safe mode está habilitado, PHP comprueba si los archivos o directorios que va a utilizar tienen el mismo UID (propietario) que el script que está siendo ejecutado.
This function used to be called pg_loimport().
The full path and file name of the file on the client filesystem from which to read the large object data.
object_idis given the function will try to create a large object with this id, else a free object id is assigned by the server. The parameter was added in PHP 5.3 and relies on functionality that first appeared in PostgreSQL 8.1.
The OID of the newly created large object, or
FALSE on failure.
Historial de cambios
The syntax of this function changed. It used to be:
int pg_lo_import ( string
Ejemplo #1 pg_lo_import() example
$database = pg_connect("dbname=jacarta");
$oid = pg_lo_import($database, '/tmp/lob.dat');
Due to a bug, OLD API does not available with PHP 4.2.0 and 4.2.1.
PHP 4.2.2 will support OLD API again and will be kept long enough.
New API will be available PHP 4.2.0 to later versions.
Due to a bug, PHP 4.2.0 and 4.2.1 does not support pg_lo_import() old API. It's fixed in PHP 4.2.2.
BTW, new API will be always available from PHP 4.2.0 to later versions. Older API will be kept long enough, also.