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 — Write to a large object
Açıklama
pg_lo_write() writes data into a large object at the current seek position.
To use the large object interface, it is necessary to enclose it within a transaction block.
Bilginize:
This function used to be called pg_lowrite().
Bağımsız Değişkenler
-
lob -
pg_lo_open()işlevinden dönen PgSql\Lob nesnesi.
-
data -
The data to be written to the large object. If
lengthis an int and is less than the length ofdata, onlylengthbytes will be written. -
length -
An optional maximum number of bytes to write. Must be greater than zero and no greater than the length of
data. Defaults to the length ofdata.
Dönen Değerler
The number of bytes written to the large object, or false on error.
Sürüm Bilgisi
| Sürüm: | Açıklama |
|---|---|
| 8.1.0 |
lob bağımsız değişkeni artık
PgSql\Lob nesnesi kabul ediyor, evvelce bir
özkaynak kabul ederdi.
|
| 8.0.0 |
length is now nullable.
|
Örnekler
Örnek 1 pg_lo_write() example
<?php
$doc_oid = 189762345;
$data = "This will overwrite the start of the large object.";
$database = pg_connect("dbname=jacarta");
pg_query($database, "begin");
$handle = pg_lo_open($database, $doc_oid, "w");
$data = pg_lo_write($handle, $data);
pg_query($database, "commit");
?>
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.
