Austin Roy Omondi
Feb 12, 2020 ⋅ 7 min read

Intro to Postgres + GraphQL with PostGraphile

Austin Roy Omondi Live long and prosper 👌

Recent posts:

Leveraging Wasp For Full-Stack Development

Leveraging Wasp for full-stack development

Learn how the Wasp, Web Application Specification, framework simplifies full-stack development by offloading repetitive code tasks.

Wisdom Ekpotu
May 27, 2024 ⋅ 11 min read
Developing Web Extensions With Wxt

Developing web extensions with the WXT library

Browser extensions are an important part of the web ecosystem. They make our lives easier and enhance our web browsing […]

Debjyoti Banerjee
May 24, 2024 ⋅ 8 min read
Bulma Css Adoption Guide: Overview, Examples, And Alternatives

Bulma CSS adoption guide: Overview, examples, and alternatives

Explore how Bulma CSS simplifies frontend development with its ease of use and customizable, responsive, pre-designed UI elements.

Timonwa Akintokun
May 23, 2024 ⋅ 10 min read
Using Mountaineer To Develop A React App With Python

Using Mountaineer to develop a React app with Python

Develop a React app with Python using the Mountaineer framework for building a simple app with integrated your frontend and backend database.

Rosario De Chiara
May 23, 2024 ⋅ 7 min read
View all posts

3 Replies to "Intro to Postgres + GraphQL with PostGraphile"

  1. Hi Austin, Thanks for this!
    I just wanted to let you know that I found this useful but you could add something in there to let people know that they should use `-s “test_schema”` to be able to see the schema in graphiql. I got stuck on this part for a bit but then after reading the postgraphile –help I was able to figure out that I should need to use `postgraphile -s “test_schema” -c “postgres:///testdb”`
    Keep up the good work!

  2. I got the same error as Dana Z, I corrected it but then I am getting ‘permission denied for schema “test_schema”‘. Can somebody help?

  3. I too has the schema issue. Below is the entire command I used to start up postgraphile:

    postgraphile -s test_schema -c “postgresql://:@localhost:5432/testdb”

    The username I specified was one that I created in the database…I gave this user “login” and “superuser” privileges (Not recommended for production systems!).

    Then on the test_schema properties page, click the security tab and grant all privileges to this new user.

    I know it’s a year later, but HTH!

Leave a Reply