Remove mention of INV_ARCHIVE.
This commit is contained in:
parent
ea41e77c22
commit
bb35e499ea
doc/src/sgml
@ -1134,7 +1134,7 @@ The oid of the large object created.
|
||||
<TITLE>Usage
|
||||
</TITLE>
|
||||
<PARA>
|
||||
mode can be any OR'ing together of INV_READ, INV_WRITE, and INV_ARCHIVE.
|
||||
mode can be any OR'ing together of INV_READ and INV_WRITE.
|
||||
The OR delimiter character is "|".
|
||||
<ProgramListing>
|
||||
[pg_lo_creat $conn "INV_READ|INV_WRITE"]
|
||||
|
@ -1,5 +1,5 @@
|
||||
<!--
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/lobj.sgml,v 1.17 2001/09/10 03:02:06 ishii Exp $
|
||||
$Header: /cvsroot/pgsql/doc/src/sgml/lobj.sgml,v 1.18 2001/09/10 04:15:41 momjian Exp $
|
||||
-->
|
||||
|
||||
<chapter id="largeObjects">
|
||||
@ -117,17 +117,13 @@ Oid lo_creat(PGconn *<replaceable class="parameter">conn</replaceable>, int <rep
|
||||
<filename>$<envar>PGROOT</envar>/src/backend/libpq/libpq-fs.h</filename>
|
||||
The access type (read, write, or both) is controlled by
|
||||
OR ing together the bits <acronym>INV_READ</acronym> and
|
||||
<acronym>INV_WRITE</acronym>. If
|
||||
the large object should be archived -- that is, if
|
||||
historical versions of it should be moved periodically to
|
||||
a special archive relation -- then the <acronym>INV_ARCHIVE</acronym> bit
|
||||
should be set. The low-order sixteen bits of mask are
|
||||
<acronym>INV_WRITE</acronym>. The low-order sixteen bits of mask are
|
||||
the storage manager number on which the large object
|
||||
should reside. For sites other than Berkeley, these
|
||||
bits should always be zero.
|
||||
The commands below create an (Inversion) large object:
|
||||
<programlisting>
|
||||
inv_oid = lo_creat(INV_READ|INV_WRITE|INV_ARCHIVE);
|
||||
inv_oid = lo_creat(INV_READ|INV_WRITE);
|
||||
</programlisting>
|
||||
</para>
|
||||
</sect2>
|
||||
|
@ -1,4 +1,4 @@
|
||||
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/Attic/pygresql.sgml,v 1.1 2001/03/04 18:54:07 petere Exp $ -->
|
||||
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/Attic/pygresql.sgml,v 1.2 2001/09/10 04:15:41 momjian Exp $ -->
|
||||
|
||||
<chapter id="pygresql">
|
||||
<title><application>PyGreSQL</application> - <application>Python</application> Interface</title>
|
||||
@ -418,7 +418,6 @@ make && make install
|
||||
<varlistentry>
|
||||
<term><varname>INV_READ</varname></term>
|
||||
<term><varname>INV_WRITE</varname></term>
|
||||
<term><varname>INV_ARCHIVE</varname></term>
|
||||
<listitem>
|
||||
<para>
|
||||
large objects access modes, used by
|
||||
@ -2253,7 +2252,7 @@ locreate(<replaceable>mode</replaceable>)
|
||||
<para>
|
||||
<function>locreate()</function> method creates a large object in the database.
|
||||
The mode can be defined by OR-ing the constants defined in the pg module
|
||||
(<literal>INV_READ, INV_WRITE</literal> and <literal>INV_ARCHIVE</literal>).
|
||||
(<literal>INV_READ and INV_WRITE</literal>).
|
||||
</para>
|
||||
</refsect1>
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user