dwyl / dwyl/postgres-schema-migration-checker

Why? What? How?

Open
#1 21 comments 0 reactions 0 assignees View on GitHub
help wanted question
Dominant language
No language data
Stars
5
Forks
0
PR merge metrics
No merged PRs in 30d

Description

@iteles Please add the photos you took of the sketches from today into this _description_ of the issue (or send them to me!) **thanks!** ⭐️

![img_0695](https://cloud.githubusercontent.com/assets/4185328/22123137/707c9656-de82-11e6-9656-008d621b1d12.JPG)
![img_0698](https://cloud.githubusercontent.com/assets/4185328/22123136/707bc42e-de82-11e6-8467-4c544f46e649.JPG)
![img_0696](https://cloud.githubusercontent.com/assets/4185328/22123139/7080b862-de82-11e6-8d5f-175e496e6534.JPG)
![img_0697](https://cloud.githubusercontent.com/assets/4185328/22123138/707f4c84-de82-11e6-9fc0-0d451a18afd2.JPG)

> Note: @alexeyklyukin has good experience with PostgreSQL and gave a Presentation on the problem at PGConf 2014: https://docs.google.com/presentation/d/1TV0bExFwVy-_d6C7A8Z2JL9Z9tvtkuZv3D58fkC3GWQ
it might be worth reaching out to him to _understand_ what the "state of the tools" is in 2017...?

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue body already contains four sketch photos; review those images and the linked PGConf 2014 presentation first. Clarify the requested documentation about the state of PostgreSQL schema-migration tools in 2017, and consider the work done only when the intended context and next steps are explicit.

Written by the indexing model from the issue text.

Assessment

Tech stack
postgresql
Domain
databases, documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.