Você procurou por: blob(binary large object) (Coreano - Inglês)

blob(binary large object)
binary large object

do not close the database connection before closing the large object resource.
warning

pg_lo_tell() returns current position (offset from the beginning of large object).
pg_lo_tell() returns current position (offset from the beginning of large object).

pg_lo_unlink() deletes a large object with the oid. returns true on success or false on failure.
pg_lo_unlink() deletes a large object with the oid.

the oid argument specifies oid of the large object to export and the pathname argument specifies the pathname of the file. it returns false if an error occurred, true otherwise.
it returns false if an error occurred, true otherwise.

php에서 postgresql의 large object 기능을 사용하려면 그것을 트랜잭션 블럭안에 포함시켜야 한다. 트랜잭션 블럭은 begin 으로 시작해서 commit 혹은 end 로 끝난다. 만약 트랜잭션이 실패하였다면 그 실패한 트랜잭션은 반드시 rollback 혹은 abort 로 끝나야 한다.
the constants below are defined by this extension, and will only be available when the extension has either been compiled into php or dynamically loaded at runtime.

pg_lo_close() closes a large object. large_object is a resource for the large object from pg_lo_open().
pg_lo_close() closes a large object. large_object is a resource for the large object from pg_lo_open().

pg_lo_create() creates a large object and returns the oid of the large object. connection specifies a valid database connection opened by pg_connect() or pg_pconnect(). postgresql access modes inv_read, inv_write, and inv_archive are not supported, the object is created always with both read and write access. inv_archive has been removed from postgresql itself (version 6.3 and above). it returns large object oid, otherwise it returns false if an error occurred.
postgresql access modes inv_read, inv_write, and inv_archive are not supported, the object is created always with both read and write access.