migrate

Opinionated SQL-powered productive roll-forward migration tool for PostgreSQL.

Data & Databases

Explore on GitHub Read Hacker News discussions

4Distinct people

4Mentions

0Explicit recommenders

836GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

Opinionated SQL-powered productive roll-forward migration tool for PostgreSQL.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year4 dated mentions

Observed mentions: 2019-11-04 04:50:00 UTC to 2023-10-30 08:13:39 UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Comments
2019	2019-01-01 00:00:00 UTC	2020-01-01 00:00:00 UTC	1	1
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	2	2
2021	2021-01-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	0	0
2022	2022-01-01 00:00:00 UTC	2023-01-01 00:00:00 UTC	0	0
2023	2023-01-01 00:00:00 UTC	2024-01-01 00:00:00 UTC	1	1

What Hacker News says

4 sources

stephane-klein·Oct 30, 2023

I just started a project and chose this stack: - SSR SvelteKit with Hydration (https://github.com/sveltejs/kit) - PostgreSQL database server - Postgres.js - PostgreSQL client for Node.js (https://github.com/porsager/postgres) - Migration powered by graphile-migrate (https://github.com/graphile/migrate) - PostgreSQL Row-Level Security (https://www.postgresql.org/docs/16/ddl-rowsecurity.html) - svelte-headlessui (https://github.com/rgossiaux/svelte-headlessui) - sveltekit-i18n (https://github.com/sveltekit-i18n/lib) - TailwindCSS (https://tailwindcss.com/) - Superforms (https://superforms.rocks/) - sveltekit-flash-message + svelte-french-toast (https://github.com/ciscoheat/sveltekit-flash-message + https://github.com/kbrgl/svelte-french-toast) Tooling : - asdf (https://asdf-vm.com/) - Docker and Docker Compose - NodeJS - pnpm - Jest for uni

Read the rest

ttest All deployed on a VM at Scaleway (https://www.scaleway.com/en/) with Bash script (https://github.com/stephane-klein/sveltekit-tendaro-webshell...) After 3 months of development on this stack, I'm very satisfied. My application is fast, light and requires very little code. Project skeleton example: https://github.com/stephane-klein/sveltekit-tendaro-webshell...

In Ask HN: If you were to build a web app today what tech stack would you choose?

ecf·Sep 11, 2020

I recently started a side project on top of Postgraphile and I had to end up scrapping it in favor of something I was more familiar with. The biggest problem is that unless the main language you’re familiar with is PL/pgSQL, you’ll eventually run into the roadblock that is having everything reside in the DB. In my case, I simply could not figure out how to use the Users table without having the password returned in all queries. I could turn off the automatically generated queries that Postgraphile made, but at that point why bother with it? Other problems are that there isn’t a mature and well established method of maintaining development, staging, and production database schemas on projects with more than one developer. Graphile makes https://github.com/graphile/migrate, however, it seems incredibly brittle and is built on a workflow tha

Read the rest

t will absolutely break production if it is slightly deviated from. I really liked using it! I just hope some of these developer ergonomics issues could be better handled.

In Show HN: Octo – Generate a serverless API from an SQL query

davecardwell·Sep 3, 2020

I agree. I’ve been using pgtyped for a recent project, along with https://github.com/graphile/migrate for migrations, and it has been great to just write SQL and not have to battle with an ORM’s abstractions.

In Show HN: ORM for TypeScript with no query-builder, supporting full SQL queries

joshuakelly·Nov 4, 2019

The Graphile folks are working on Graphile Migrate to improve the migrations story: https://github.com/graphile/migrate Separately, I've got a fairly advanced setup of schema/seed lifecycle flow in a Graphile-powered application that will likely be open-sourced at some point. The simplicity of the architecture makes these things relatively easy to spin up from scratch.

In PostgREST