Columns
| Column | Type | Size | Nulls | Auto | Default | Children | Parents | Comments | ||
|---|---|---|---|---|---|---|---|---|---|---|
| id | INT | 10 | √ | null |
|
|
Primary id for this table. This uniquely identifies the row. |
|||
| germinatebase_id | INT | 10 | null |
|
|
Foreign key germinatebase (germinatebase.id). |
||||
| parent_id | INT | 10 | null |
|
|
Foreign key germinatebase (germinatebase.id). This is the parrent of the individual identified in the germinatebase_id column. |
||||
| relationship_type | enum('M', 'F', 'OTHER') | 5 | OTHER |
|
|
Male or Female parent. Should be recorded as ‘M’ (male) or ‘F’ (female). |
||||
| pedigreedescription_id | INT | 10 | null |
|
|
Foreign key pedigreedescriptions (pedigreedescriptions.id). |
||||
| relationship_description | MEDIUMTEXT | 16777215 | √ | null |
|
|
Can be used as a meta-data field to describe the relationships if a complex rellationship is required. Examples may include, ‘is a complex cross containing’, ‘F4 generation’ and so on. This is used by the Helium pedigree visualiztion tool. |
|||
| created_on | DATETIME | 26 | √ | CURRENT_TIMESTAMP |
|
|
When the record was created. |
|||
| updated_on | TIMESTAMP | 26 | √ | CURRENT_TIMESTAMP |
|
|
When the record was updated. This may be different from the created on date if subsequent changes have been made to the underlying record. |
Indexes
| Constraint Name | Type | Sort | Column(s) |
|---|---|---|---|
| PRIMARY | Primary key | Asc | id |
| pedigrees_ibfk_germinatebase | Performance | Asc | germinatebase_id |
| pedigrees_ibfk_germinatebase_parent | Performance | Asc | parent_id |
| pedigrees_ibfk_pedigreedescriptions | Performance | Asc | pedigreedescription_id |