manjobi Wiki
Brought to you by:
adobeadmin,
alexmohr
Menu
▾
▴
Database Tables Log in to Edit
Changes
The changes database contains all the changes the application has processed. Each entry is identified by a changelist, and the depot from which the changelist came from. It contains the following columns:
| changelist | the changelist |
| depotID | the associated depot from which this changelist came from, matching depotID entry in "depots" table |
| changeID | a unique identifier for the particular changelist/depotID combination |
| client | the description given to this changelist |
| changeDate | the data/time of this changelist |
| userID | the user who checked in this changelist, matching userID entry in the "users" table |
Depots
This table is to create a unique ID for each depot encountered. The two keys are depotID and name.
FileChanges
Each entry of this table signifies a unique file-action with associated unique ID filechangeID, that is action against a file (i.e. add/delete/integrate). It contains the following columns:
| filechangeID | a unique identifier for this file-action |
| changeID | the unique identifier from the "changes" table describing which change brought this file-action |
| fileID | the unique identifier from the "files" table describing the file associated with this file-action |
| revision | the revision of the file of this file-action |
| action | the action of the file-action |
Files
The files table contains all the files encountered by the application, with an associated unique identifier fileID. It contains the following columns:
| fileID | the unique identifier of this file |
| depotID | the depotID matching an entry to the "depots" table from which this file comes |
| fileName | the path to the file in the depot |
| parentID | the fileID of the parent of this from (from which this file was branched from) |
| parentRev | the revision of the parentID from which this file came from |
LineDiffs
This table contains regions of files modified by users, and the associated action. It consists of the following columns:
| filechangeID | an entry matching the "filechanges" table describing which file+revision this occured. |
| b_line | the start line where the diff took place |
| num | the number of lines for this diff |
| action | the type of edit the user performed (add/delete/change) |
Ownerships
This table contains complete ownership of every text file processed for each revision available. In order to re-construct the ownership of a particular file one must collage all the entries of a particular filechangeID. It is similar to the linediffs table.
| filechangeID | an entry matching the "filechanges" table describing which file+revision this is for. |
| b_line | the start line of a user's ownership in the file |
| e_line | the end line of a user's ownership in the file |
| userID | the unique id of the user to which this region is attributed, with matching entry in the "users" table |
Users
This table associates a unique ID with each user. The consists of a userID and name column.
Related
Discussion
Anonymous