Austin Roy Omondi
Feb 12, 2020 ⋅ 7 min read

Intro to Postgres + GraphQL with PostGraphile

Austin Roy Omondi Live long and prosper 👌

Recent posts:

Using Defer In Angular 17 To Implement Lazy Loading

Using defer in Angular 17 to implement lazy loading

Angular’s new `defer` feature, introduced in Angular 17, can help us optimize the delivery of our apps to end users.

Lewis Cianci
Dec 4, 2023 ⋅ 10 min read

Using ElectricSQL to build a local-first application

ElectricSQL is a cool piece of software with immense potential. It gives developers the ability to build a true local-first application.

Rahul Padalkar
Dec 1, 2023 ⋅ 11 min read
Using Rust And Leptos To Build Beautiful Declarative User Interfaces

Using Rust and Leptos to build beautiful, declarative UIs

Leptos is an amazing Rust web frontend framework that makes it easier to build scalable, performant apps with beautiful, declarative UIs.

Eze Sunday
Nov 30, 2023 ⋅ 10 min read
5 Best JavaScript Multi-Dimensional Array Libraries

5 best JavaScript multidimensional array libraries

Learn more about the 5 best JavaScript libraries for dealing with multidimensional arrays, such as ndarray, math.js, and NumJs.

Pascal Akunne
Nov 30, 2023 ⋅ 4 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