typelevel / typelevel/skunk

Feature reqest: migrations.

Open
#959 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Scala
Stars
1.7k
Forks
175
Avg merge
5d 14h
Merged PRs (30d)
9

Description

Projects like Flyway and Liquibase enable schema creation and migration. They are however not multiplatform. It would be nice it Skunk provided a form of migration tooling.

I don't think there is any point in implementing all the functionality of the mentioned projects, but just the ability to perform simple forward migrations would be a great QoL feature (in my opinion). It allows for easy deployments and makes it easy to keep the schema in sync when developing in a team.

The obvious first question to ask/answer is if this is something that should be handled by Skunk, or if it should come from some external library/tool.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing Skunk's existing database capabilities with the migration approaches used by Flyway and Liquibase. Investigate whether simple forward migrations belong in Skunk or an external library/tool, then define the smallest useful scope for keeping PostgreSQL schemas synchronized during deployments and team development.

Written by the indexing model from the issue text.

Assessment

Tech stack
postgres, scala
Domain
databases
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.