Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Build an ordered playlist API with Go, gqlgen and Ent on ClickHouse Managed Postgres. Authenticated account tokens scope reads and writes; creation is atomic, and reordering uses a parent lock, observed revision, exact membership validation and deferred position uniqueness. GraphQL mutations permit one expanded top-level field, and bounded eager reads keep nested metadata coherent.
Validation includes six native unit cases, eleven distinct Cloud HTTP cases across full and targeted runs, two native Cloud controls for TLS and snapshot coherence, actual deferred COMMIT failure, measured three-statement eager reads at both fixture sizes, clean native generation/build and a real graceful process replacement. The dedicated Cloud fixture has been deleted after review. CI runs module verification, formatting, unit tests, deterministic generation and compilation without Cloud credentials.
The README includes role-separated setup, migration, TLS, request examples and cleanup. Shared runtime database credentials remain trusted; API ownership is not RLS. The companion article remains a local unpublished draft.