| | 1 | = The BOINC database = |
|---|
| | 2 | |
|---|
| | 3 | BOINC stores information in a MySQL database. The main tables are: |
|---|
| | 4 | |
|---|
| | 5 | platform :: |
|---|
| | 6 | Compilation targets of the core client and/or applications. |
|---|
| | 7 | app:: |
|---|
| | 8 | Applications. The core client is treated as an application; its name is 'core_client'. |
|---|
| | 9 | app_version:: |
|---|
| | 10 | Versions of applications. Each record includes a URL for downloading the executable, and the MD5 checksum of the executable. |
|---|
| | 11 | user:: |
|---|
| | 12 | Describes users, including their email address, name, web password, and authenticator. |
|---|
| | 13 | host:: |
|---|
| | 14 | Describes hosts. |
|---|
| | 15 | workunit:: |
|---|
| | 16 | Describes workunits. The input file descriptions are stored in an XML document in a blob field. Includes counts of the number of results linked to this workunit, and the numbers that have been sent, that have succeeded, and that have failed. |
|---|
| | 17 | result:: |
|---|
| | 18 | Describes results. Includes a 'state' (whether the result has been dispatched). Stores a number of items relevant only after the result has been returned: CPU time, exit status, and validation status. |
|---|
| | 19 | |
|---|
| | 20 | The database is created by the [MakeProject make_project] script. Normally you don't have to directly examine or manipulate the database. If you need to, you can use the MySQL command-line interpreter or BOINC's [HtmlOps administrative web interface]. |
|---|
