Review the database schema

[UlisesGascon]

It seems like the relations between the tables might have room for improvement. We want to make sure that relation fields like github_organization.project_id are not NULLABLE.

Additionally, we should review the datatypes for the columns to ensure they are aligned with the content.

[bjohansebas]

i can help with this 😄

[UlisesGascon]

I assigned this issue to you, let me know if you need help :)

[bjohansebas]

We want to ensure that the IDs are numbers, or we could switch them to UUID?

[bjohansebas]

Here I will write about the changes:

• github_organizations: None, all match their type in the API.
• github_repositories:
  • github_organization_id not null

[bjohansebas]

According to my review, only one change to the schema would be needed. I can't do it myself until next year, maybe someone else would like to do it.

[telekosmos]

According to my review, only one change to the schema would be needed. I can't do it myself until next year, maybe someone else would like to do it.

For what I've seen and without knowing some aspects of the schema, agree 👍 , NOT NULL constraints didn't seem to be that bad.

[UlisesGascon]

I think that with the changes in #160 and #167 we are good to go and we can close this issue, but we can re-open it again if we need more work on this again.