Setup: database design

[RobStallion]

Design a database that will work well with the technologies being used and also deliver everything needed for the application.

The schemas should be clear and easy to understand. They should also be designed to work well with autoform so that we can quickly and easily create the forms needed for the application.

We will also be designing the database in an append only style. See here and here for more info

[RobStallion]

[tiffany-tang]

@RobStallion As discussed earlier, at this stage, we will not be asking participating users for their first names and email. What will happen during the November testing is we will randomly distribute the usernames and pins to them.

During dev, we will provide you with the number of children taking part and the teacher's email as the Trusted Adult contact (that will be dependent on whether the teacher is willing to take part in this way, but hopefully we will have a discussion with the school soon).

[RobStallion]

@tiffany-tang Thanks for clearing that up for us. We will remove email and first_name from the user table and replace them with username.

[RobStallion]

Have had a thought on the current design for the emotion_log table. I didn't think it was best to create a row for each emotion in the table when only one will be inserted each time we insert into this table.

Redesign

The schema will be set up to work how sql enum type works. We will be able to set a list of emotions that will be able to be inserted. If any other string is tried to be inserted it will return the changeset with an error.

[RobStallion]

Diagram in comment above should also contain a field called emotion_id which will be type integer.