db: rough draft of db init

[ear7h]

The database schema does describe the objects perfectly. For example some database objects may be melded together when used within the system.

closes #30

[AdamW19]

It's a pretty good rough draft, I'll assume we may need to add/delete/modify some of the columns as development continues.

Maybe for the events table we could add stuff like "location" or "when" (in unix epoch). For orgs, maybe add "social media tag", "website", or "org type"?

Just a few suggestions

[ear7h]

@AdamW19 Yea, I'll upload a README that has instructions on migrations. But basically when we want to change something to the database we'll add another file $(date "%Y-%m-%d")_migration_description.sql that will get run on the production database.

And @Bigoni if you'd like to add some of those fields that would be appreciated, you can just change this one file (you don't have to go through the process above). Per our discord convo you can verify the correctness of the file by using sqlite3 on the ieng6 servers.

[Bigoni]

If we have org emails, we likely want user emails as well.

[ear7h]

@Bigoni The user email is on the users table itself. The reason being, we could potentially have multiple emails for a single org, but I don't think that should be the case for users.