PostGraphile

A GraphQL schema created by reflection over a PostgreSQL schema.

Documentation: graphile.org/postgraphile

This project was previously named PostGraphQL, for version 3 of PostGraphQL see the v3 branch.

This is the BETA version of PostGraphile v4 (previously known as PostGraphQL)

Make sure you stay up to date via the releases.

Due to a few breaking changes we recommend that anyone starting fresh uses v4 over v3 despite the beta status - v3 will not be receiving ongoing maintenance. All the anticipated breaking changes were ironed out during the alpha phase, breaking changes will only be made in the beta if absolutely necessary.

A migration guide if you're coming from v3 is here and you can check out some of the new features here

The strongly typed GraphQL data querying language is a revolutionary new way to interact with your server. Similar to how JSON very quickly overtook XML, GraphQL will likely overtake REST. Why? Because GraphQL allows us to express our data in the exact same way we think about it.

The PostgreSQL database is the self acclaimed “world’s most advanced open source database” and even after 20 years that still rings true. PostgreSQL is the most feature rich SQL database available and provides an excellent public reflection API giving its users a lot of power over their data. And despite being over 20 years old, the database still has frequent releases.

With PostGraphile, you can access the power of PostgreSQL through a well designed GraphQL server. PostGraphile uses PostgreSQL reflection APIs to automatically detect primary keys, relationships, types, comments, and more providing a GraphQL server that is highly intelligent about your data.

PostGraphile holds a fundamental belief that a well designed database schema should be all you need to serve well thought out APIs. PostgreSQL already has amazing user management and relationship infrastructure, why duplicate that logic in a custom API? PostGraphile is likely to provide a more performant and standards compliant GraphQL API then any created in house. Focus on your product and let PostGraphile manage how the data gets to the product.

For a critical evaluation of PostGraphile to determine if it fits in your tech stack, read evaluating PostGraphile for your project.

Introduction

Watch a talk by the original author Caleb at GraphQL Summit for a fast 7 minute introduction to using the PostGraphile project. This was using v2; we're now up to v4 which has many more bells and whistles!

Usage

First install using npm:

npm install -g postgraphile

…and then just run it! By default, PostGraphile will connect to your local database at postgres://localhost:5432 and introspect the public schema.

postgraphile

For information about how to change these defaults, just run:

postgraphile --help

You can also use PostGraphile as native HTTP, Connect, Express, or Koa (experimental) middleware. Just import postgraphile:

import { createServer } from "http";
import postgraphile from "postgraphile";

createServer(postgraphile());

For more information around using PostGraphile as a library, and the options the API expects read the library usage article.

Check out hapi-postgraphile if you're interested in using PostGraphile as a hapi server plugin.

There is also a docker image for running PostGraphile maintained by @angelosarto, simply pass the same options to the docker container:

# TODO: these commands are NOT correct right now - we need to publish postgraphile!
# In the interrim you can use older version by replacing this with `postgraphql/postgraphql`
docker pull graphile/postgraphile
docker run graphile/postgraphile --help

To connect to a database and expose the PostGraphile port try this:

# TODO: make this work!
docker run -p 5000:5000 graphile/postgraphile --connection postgres://POSTGRES_USER:POSTGRES_PASSWORD@POSTGRES_HOST:POSTGRES_PORT/POSTGRES_DATABASE

Also make sure to check out the forum example and especially step by step tutorial for a demo of a PostGraphile compliant schema and authentication.

Benefits

PostGraphile uses the joint benefits of PostgreSQL and GraphQL to provide a number of key benefits.

Automatic Relation Detection

Does your table’s authorId column reference another table? PostGraphile knows and will give you a field for easily querying that reference.

A schema like:

create table post (
  id serial primary key,
  author_id int non null references user(id),
  headline text,
  body text,
  ...
);

Can query relations like so:

{
  allPosts {
    edges {
      node {
        headline
        body
        author: userByAuthorId {
          name
        }
      }
    }
  }
}

Custom Mutations and Computed Columns

Procedures in PostgreSQL are powerful for writing business logic in your database schema, and PostGraphile allows you to access those procedures through a GraphQL interface. Create a custom mutation, write an advanced SQL query, or even extend your tables with computed columns! Procedures allow you to write logic for your app in SQL instead of in the client all while being accessible through the GraphQL interface.

So a search query could be written like this:

create function search_posts(search text) returns setof post as $$
  select *
  from post
  where
    headline ilike ('%' || search || '%') or
    body ilike ('%' || search || '%')
$$ language sql stable;

And queried through GraphQL like this:

{
  searchPosts(search: "Hello world", first: 5) {
    pageInfo {
      hasNextPage
    }
    totalCount
    edges {
      cursor
      node {
        headline
        body
      }
    }
  }
}

For more information, check out our procedure documentation and our advanced queries documentation.

Advanced Watch Mode

Running PostGraphile in watch mode will get you the best experience for iterating on a GraphQL API in the whole GraphQL ecosystem.

postgraphile --watch

PostGraphile will watch your Postgres database for changes. New tables, updated columns, new procedures, and more! When these changes are detected PostGraphile will re-create your schema and will automatically update any opened GraphiQL windows with the new schema while preserving your navigation state in the documentation viewer.

Fully Documented APIs

Introspection of a GraphQL schema is powerful for developer tooling and one element of introspection is that every type in GraphQL has an associated description field. As PostgreSQL allows you to document your database objects, naturally PostGraphile exposes these documentation comments through GraphQL.

Documenting PostgreSQL objects with the COMMENT command like so:

create table user (
  username text non null unique,
  ...
);

comment on table user is 'A human user of the forum.';
comment on column user.username is 'A unique name selected by the user to represent them on our site.';

Will let you reflect on the schema and get the JSON below:

{
  __type(name: "User") { ... }
}

{
  "__type": {
    "name": "User",
    "description": "A human user of the forum.",
    "fields": {
      "username": {
        "name": "username",
        "description":
          "A unique name selected by the user to represent them on our site."
      }
    }
  }
}

UI For Development Comes Standard

GraphiQL is a great tool by Facebook to let you interactively explore your data. When development mode is enabled in PostGraphile, the GraphiQL interface will be automatically displayed at your GraphQL endpoint.

Just navigate with your browser to the URL printed to your console after starting PostGraphile and use GraphiQL with your data! Even if you don’t want to use GraphQL in your app, this is a great interface for working with any PostgreSQL database.

Token Based Authorization

PostGraphile lets you use token based authentication with JSON Web Tokens (JWT) to secure your API. It doesn’t make sense to redefine your authentication in the API layer, instead just put your authorization logic in the database schema! With an advanced grants system and row level security, authorization in PostgreSQL is more than enough for your needs.

PostGraphile follows the PostgreSQL JSON Web Token Serialization Specification for serializing JWTs to the database for your use in authorization. The role claim of your JWT will become your PostgreSQL role and all other claims can be found under the jwt.claims namespace (see retrieving claims in PostgreSQL).

To enable token based authorization use the --secret <string> command line argument with a secure string PostGraphile will use to sign and verify tokens. And if you don’t want authorization, just don’t set the --secret argument and PostGraphile will ignore all authorization information!

Cursor Based Pagination For Free

There are some problems with traditional limit/offset pagination and realtime data. For more information on such problems, read this article.

PostGraphile not only provides limit/offset pagination, but it also provides cursor based pagination ordering on the column of your choice. Never again skip an item with free cursor based pagination!

Relay Specification Compliant

You don’t have to use GraphQL with React and Relay, but if you are, PostGraphile implements the brilliant Relay specifications for GraphQL. Even if you are not using Relay your project will benefit from having these strong, well thought out specifications implemented by PostGraphile.

The specific specs PostGraphile implements are:

Documentation

Requirements

We officially only support Node v8.6+; if you require support for an earlier version of Node please raise an issue explaining why you can't update to the latest Node LTS and we'll see what we can do.

We officially support PostgreSQL 9.6+, but the tests run against PostgreSQL 9.4 so all our core functionality should work on that DB too.

We don't have much in the way of support for PG10-only features yet - if you'd like to sponsor development of these, please get in touch!

The Graphile suite of tools are developed under Mac OS X and tested under Linux, since we're a small project we don't have the resources to ensure strong Windows support, however we would like to support that platform so if you have any issues related to operating system, please raise an issue or — even better — a pull request!

Contributing

Want to help testing and developing PostGraphile? Check out the contributing document to get started quickly!

Maintenance

The maintainer of this project is @Benjie - follow him on Twitter!

Thanks

Thanks so much to the people working on PostgREST which was definitely a huge inspiration for this project!

A humongous, heart-felt, thank you to the original author of PostGraphile - Caleb Meredith - for everything he put into PostGraphile! He's now graduated from the project and we all wish him the best for his future ventures!

Even more thanks to each and every sponsor of the project - without their help progress would be a lot slower! Please join them in supporting this project 🙏

Thanks and enjoy 👍

apapacy / postgraphile Goto Github PK

postgraphile's Introduction