Epic: Define (Ecto) PostgreSQL Database Schema

[nelsonic]

All the "Meta Data" (anything that is not an issue comment, which is Markdown/"Rich Text") of issues will be stored in a PostgreSQL Database.

With reference to the GitHub API for users, issues and comments, we need to create the Ecto (Database) Schema for the three DB tables. We are going to "normalise" the data and let Ecto construct the queries.

• [ ] Users: https://developer.github.com/v3/users
• [x] Issues: https://developer.github.com/v3/issues
• [x] Comments: https://developer.github.com/v3/issues/comments

Our aim is to match the field names in the GitHub API exactly so we keep an exact copy the data that people can easily download if they want to have a Local Copy. (don't worry, we aren't building the download feature yet!)

[Cleop]

Relates to https://github.com/dwyl/github-backup/issues/5

In the long run we might want these two tables to help us display our UI better but for now if people are accessing their comments directly from the issue then they wouldn't be necessary.

Organisations
ID
Organisation name

Repositories
ID
Repo name

Do people think we should include them in our schema now or add them later if necessary?

[nelsonic]

@Cleop if we know the desired schema up-front then we should create it as close to the "long term" as possible.

[Cleop]

Do we need the avatar url in our schema for displaying the user's photo next to their comments?

[nelsonic]

@Cleop yeah, we should save the "avatar_url". For now please assume we are storing all the info for a user. Thanks.

[Cleop]

Still to do #46