Epic: Define (Ecto) PostgreSQL Database Schema

Open
#15 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
elixir, postgresql
Domain
databases

Research direction

Start with the linked GitHub API documentation for users, issues, and issue comments, then inspect the repository to find its Ecto schema and migration entry points. Done means defining normalized database tables for all three resources while preserving the GitHub API field names exactly; the checklist shows issues and comments as complete but users still outstanding.

Written by the indexing model from the issue text.

Description

enhancement epic T1h technical

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.

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!)

Dominant language
Elixir
Stars
33
Forks
3
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dwyl/github-backup

All issues in dwyl/github-backup

Similar issues

More Elixir issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.