Edgewall Software

Changes between Version 1 and Version 2 of TracDev/DatabaseSchema


Ignore:
Timestamp:
Apr 9, 2007, 9:04:31 PM (15 years ago)
Author:
Christian Boos
Comment:

Added missing session_attribute table and some wiki syntax fixes

Legend:

Unmodified
Added
Removed
Modified
  • TracDev/DatabaseSchema

    v1 v2  
    44
    55|| '''Table Name''' || '''Purpose''' ||
    6 || {{{attachment}}} || Descriptions of attachments (files themselves are stored on disk). ||
    7 || {{{auth_cookie}}} || User login cookies. ||
    8 || {{{component}}} || Values that can be used in a ticket's "component" field.  The {{{owner}}} column is used as the default assignee for new tickets, if not overridden at the time of ticket submission. ||
    9 || {{{enum}}} || Maps integer IDs for issues' priorities, severities, etc. to human-readable names. ||
    10 || {{{milestone}}} || Project milestones. ||
    11 || {{{node_change}}} || For every changeset (as identified by the revision number), this table contains the nodes (i.e. files or directories) that have been added/modified/deleted. ||
    12 || {{{permission}}} || Username/action pairs describing who's allowed to do what. This table's contents also hold permission groups. ||
    13 || {{{report}}} || Stores the SQL to generate canned database reports. ||
    14 || {{{revision}}} || Changesets, containing the revision number, author, time, and log message.  The list of files and directories modified by a changeset can be found by joining with {{{node_change}}} on the {{{rev}}} column. ||
    15 || {{{session}}} || Information about user settings, including name, email, and diff options. ||
    16 || {{{system}}} || System information such as the database version. ||
    17 || {{{ticket}}} || Tickets. ||
    18 || {{{ticket_change}}} || Changes to tickets, on a field-by-field basis.  The field value {{{comment}}} is special: it associates a comment with a set of field changes. ||
    19 || {{{ticket_custom}}} || The values of custom ticket fields. ||
    20 || {{{version}}} || As in {{{component}}} and {{{milestone}}}, this holds the options of the drop-down {{{version}}} list on the ticket form. Every version can have a {{{time}}} set, although that is not presently used other than for ordering the list of versions in the UI. ||
    21 || {{{wiki}}} || Wiki pages (including old revisions). ||
     6|| `attachment` || Descriptions of attachments (the files themselves are stored on disk). ||
     7|| `auth_cookie` || User login cookies. ||
     8|| `component` || Values that can be used in a ticket's "component" field.  The `owner` column is used as the default assignee for new tickets, if not overridden at the time of ticket submission. ||
     9|| `enum` || Maps integer IDs for issues' priorities, severities, etc. to human-readable names. ||
     10|| `milestone` || Project milestones. ||
     11|| `node_change` || 1^st^ half of the repository cache: for every changeset (as identified by the revision number), this table contains the nodes (i.e. files or directories) that have been added/modified/deleted. ||
     12|| `permission` || Username/action pairs describing who's allowed to do what. This table's contents also hold permission groups. ||
     13|| `report` || Stores the SQL to generate canned database reports. ||
     14|| `revision` || 2^nd^ hald of the repository cache: changesets, containing the revision number, author, time, and log message.  The list of files and directories modified by a changeset can be found by joining with `node_change` on the `rev` column. ||
     15|| `session` || Last user visit time. ||
     16|| `session_attribute` || Information about user settings, including name, email, and diff options. ||
     17|| `system` || System information such as the database version and repository cache metadata  ||
     18|| `ticket` || Tickets. ||
     19|| `ticket_change` || Changes to tickets, on a field-by-field basis.  The field value `comment` is special: it associates a comment with a set of field changes. ||
     20|| `ticket_custom` || The values of custom ticket fields. ||
     21|| `version` || As in `component` and `milestone`, this holds the options of the drop-down `version` list on the ticket form. Every version can have a `time` set, although that is not presently used other than for ordering the list of versions in the UI. ||
     22|| `wiki` || Wiki pages (including old revisions). ||
    2223
    2324----