Just for the record, a user must be a superuser (database owner) in order to invoke pg_lo_open() (though pg_lo_create() may be invoked...). This opens a gigantic security hole in the db. If a user is not a superuser, db will raise an error with message "Can't create Large Object.".
Thus, imho, one should use pg_escape_bytea() instead.
pg_lo_open
(PHP 4 >= 4.2.0, PHP 5, PHP 7, PHP 8)
pg_lo_open — Open a large object
Description
pg_lo_open() opens a large object in the database and returns an PgSql\Lob instance so that it can be manipulated.
Warning
Do not close the database connection before closing the PgSql\Lob instance.
To use the large object interface, it is necessary to enclose it within a transaction block.
Note:
This function used to be called pg_loopen().
Parameters
-
connection -
An PgSql\Connection instance. When
connectionis unspecified, the default connection is used. The default connection is the last connection made by pg_connect() or pg_pconnect().WarningAs of PHP 8.1.0, using the default connection is deprecated.
-
oid -
The OID of the large object in the database.
-
mode -
Can be either "r" for read-only, "w" for write only or "rw" for read and write.
Return Values
An PgSql\Lob instance, or false on failure.
Changelog
| Version | Description |
|---|---|
| 8.1.0 | Returns an PgSql\Lob instance now; previously, a resource was returned. |
| 8.1.0 |
The connection parameter expects an PgSql\Connection
instance now; previously, a resource was expected.
|
Examples
Example #1 pg_lo_open() example
<?php
$database = pg_connect("dbname=jacarta");
pg_query($database, "begin");
$oid = pg_lo_create($database);
echo "$oid\n";
$handle = pg_lo_open($database, $oid, "w");
echo "$handle\n";
pg_lo_write($handle, "large object data");
pg_lo_close($handle);
pg_query($database, "commit");
?>
add a note
User Contributed Notes 1 note
metator at netcabo dot pt ¶
19 years ago
