Make statement generation and ordering independent

Open
#131 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
go, postgresql, sql
Domain
databases

Research direction

No files, tests, or entry points are named. Start by tracing the nested SQL generators and how they currently flatten SQL graphs, then inspect how generated statements are represented and ordered. Done means every generated statement is a SQL node, nested graphs are unioned into the larger graph, and each statement has a globally unique referenceable ID.

Written by the indexing model from the issue text.

Description

To do this, every generated statement should be a SQL node. Instead of flattening sql graphs in nested sql generators, we leave them as sql graphs and union them into the larger graph.

Every sql statement should have a globally unique id that can be referenced.

Dominant language
Go
Stars
884
Forks
82
No merged PRs in 30d

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.

More from stripe/pg-schema-diff

All issues in stripe/pg-schema-diff

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.