Add correct participant fk to availibility table

This commit is contained in:
rui hildt 2020-05-05 12:17:21 +02:00
parent 6ae2f6db17
commit c4ebcbb9bd
1 changed files with 12 additions and 11 deletions

View File

@ -604,17 +604,18 @@ A json object for the deleted possible date with `id`, `meeting_id` and `possibl
### **Availibility** | `availibility`
| field | data type | metadata |
| :--------------- | :-------- | :--------------------------------- |
| id | int | primary key, auto-increment |
| participant_id | int | foreign key, required |
| possible_date_id | int | foreign key, required |
| preference | boolean | `0` (ideal) or `1` (yes), required |
| start_time | timestamp | required |
| end_time | timestamp | required |
| timezone | varchar | required |
| created_at | datetime | generated by database |
| updated_at | datetime | generated by database |
| field | data type | metadata |
| :--------------- | :-------- | :-------------------------------------------- |
| id | int | primary key, auto-increment |
| account_id | int | foreign composite key (participant), required |
| meeting_id | uuid | foreign composite key (participant), required |
| possible_date_id | int | foreign key, required |
| preference | boolean | `0` (ideal) or `1` (yes), required |
| start_time | timestamp | required |
| end_time | timestamp | required |
| timezone | varchar | required |
| created_at | datetime | generated by database |
| updated_at | datetime | generated by database |
#### Add an availibility for a possible date