File: dbmopen.xml

package info (click to toggle)
php-doc 20061001-1
  • links: PTS
  • area: non-free
  • in suites: etch, etch-m68k
  • size: 45,764 kB
  • ctags: 1,611
  • sloc: xml: 502,485; php: 7,645; cpp: 500; makefile: 297; perl: 161; sh: 141; awk: 28
file content (64 lines) | stat: -rw-r--r-- 2,398 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
<?xml version="1.0" encoding="iso-8859-1"?>
<!-- $Revision: 1.4 $ -->
<!-- splitted from ./en/functions/dbm.xml, last change in rev 1.2 -->
  <refentry id="function.dbmopen">
   <refnamediv>
    <refname>dbmopen</refname>
    <refpurpose>Opens a DBM database</refpurpose>
   </refnamediv>
   <refsect1>
    <title>Description</title>
     <methodsynopsis>
      <type>resource</type><methodname>dbmopen</methodname>
      <methodparam><type>string</type><parameter>filename</parameter></methodparam>
      <methodparam><type>string</type><parameter>flags</parameter></methodparam>
     </methodsynopsis>
    <para>
     The first argument is the full-path filename of the DBM file to
     be opened and the second is the file open mode which is one of
     "r", "n", "c" or "w" for read-only, new (implies read-write, and
     most likely will truncate an already-existing database of the
     same name), create (implies read-write, and will not truncate an
     already-existing database of the same name) and read-write
     respectively.
    </para>
    <para>
     Returns an identifier to be passed to the other DBM functions on
     success, or &false; on failure.
    </para>
    <para>
     If NDBM support is used, NDBM will actually create <filename>filename.dir</filename>
     and <filename>filename.pag</filename> files. GDBM only uses one file, as does the
     internal flat-file support, and Berkeley DB creates a
     <filename>filename.db</filename> file. Note that PHP does its own
     file locking in addition to any file locking that may be done by
     the DBM library itself. PHP does not delete the
     <filename>.lck</filename> files it creates. It uses these files
     simply as fixed inodes on which to do the file locking. For more
     information on DBM files, see your Unix man pages, or obtain
     <ulink url="&url.gdbm;">GNU's GDBM</ulink>.
    </para>
    &note.sm.uidcheck;
   </refsect1>
  </refentry>

<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:1
sgml-indent-data:t
indent-tabs-mode:nil
sgml-parent-document:nil
sgml-default-dtd-file:"../../../../manual.ced"
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
End:
vim600: syn=xml fen fdm=syntax fdl=2 si
vim: et tw=78 syn=sgml
vi: ts=1 sw=1
-->