Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add credible content model #38

Merged
merged 4 commits into from
Sep 28, 2018
Merged

Add credible content model #38

merged 4 commits into from
Sep 28, 2018

Conversation

slifty
Copy link
Member

@slifty slifty commented Sep 27, 2018

The credible content model is going to store... credible content!
Baiscally, this will hold scraped text from publications that we want to
apply truth goggles to.

This is the very first schema and model we've tried to make.

Issue #27 Scrape The Facts

@slifty slifty requested a review from crupar September 27, 2018 20:01
The credible content model is going to store... credible content!
Baiscally, this will hold scraped text from publications that we want to
apply truth goggles to.

This is the very first schema and model we've tried to make.

Issue #27 Scrape The Facts
The schema links up the previously specified model to GraphQL.  It makes
it possible to look up the objects.

Issue #27 Scrape The Facts
The example was there so we could use it as a template for our schemas.
Now that we have one, we don't need the example any longer.
These are changes that got lost somewhere in the mix.  They fix the
ability to run migrations and interact with the database.
@slifty slifty force-pushed the 27-article-scrape-schema branch from 48c654e to eb47774 Compare September 27, 2018 21:06
@slifty slifty merged commit ee1595f into master Sep 28, 2018
@slifty slifty deleted the 27-article-scrape-schema branch September 28, 2018 02:17
@knowtheory
Copy link
Contributor

Hey so i just caught this after i inspected the database after doing a sequelize db:migrate (thanks @crupar for the instructions on how to do this), but @slifty why are the models in the database upper cased rather than snake cased? Is there a convention you prefer here? Cause generally speaking using upper case table names means that you will always have to quote them if querying in SQL:

truthgoggles_development=# select * from "SequelizeMeta";
                   name                    
-------------------------------------------
 20180927153818-create-credible-content.js
(1 row)

truthgoggles_development=# select * from SequelizeMeta;
ERROR:  relation "sequelizemeta" does not exist
LINE 1: select * from SequelizeMeta;
                      ^

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants