DBSCHEMA revision 1.3 1 There are three tables in the database at present:
2
3 (1) mandb:
4 This is the main FTS table which contains all the content from
5 man pages
6
7 COLUMN NAME DESCRIPTION
8 1. section Section number of the page
9 2. name The name of the page
10 3. name_desc The one line description from the NAME section
11 4. desc Contains the content from DESCRIPTION
12 section and any other section which
13 is not indexed in a separate column.
14 5. lib The LIBRARY section
15 6. return_vals RETURN VALUES section
16 7. env ENVIRONMENT section
17 8. files FILES section
18 9. exit_status EXIT STATUS section
19 10. diagnostics DIAGNOSTICS section
20 11. errors ERRORS section
21 12. md5_hash md5 hash of the man page (UNIQUE)
22 13. machine The machine architecture (if any) for which this page is
23 relevant.
24
25 (2) mandb_meta:
26 This table contains md5 hashes of all the indexed man
27 pages. This is there to make sure we do not index
28 the same man page twice, i.e. to prevent indexing
29 hardlinks.
30
31 COLUMN NAME DESCRIPTION
32 1. device (dev_t)Logical device number from stat(2)
33 2. inode (ino_t)Inode number from stat(2)
34 3. mtime Last modification time from stat(2)
35 4. file Absolute path name (UNIQUE constraint)
36 5. md5_hash MD5 Hash of the man page (UNIQUE)
37 6. id A unique integer ID for the page, which
38 refers to the docid column in mandb (Implicit foreign
39 key?) PRIMARY KEY
40 {device, inode} form a UNIQUE index
41
42 (3) mandb_links:
43 This is an index of all the hard/soft links of the man
44 pages. The list of the linked pages is usually obtained
45 from the multiple .Nm entries in the page.
46
47 COLUMN NAME DESCRIPTION
48 1. link The name of the hard/soft link (index)
49 2. target Name of the target page to which it points
50 3. section The section number
51 4. machine The machine architecture (if any) for which
52 the page is relevant
53 5. md5_hash MD5 Hash of the target man page.
54 6. name_desc The one line description from the NAME section
55