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
1 participant
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.
A trusted loopback customer workbench preserves two operators' edits with revision checks: one transaction conditionally updates a profile and appends its history; stale submissions return 409 with the original form retained. A separate bounded activity request uses pg_clickhouse and a restricted reporting pool to read synthetic ClickHouse events through next.jdbc. Includes pinned direct/transitive dependencies, migrations, explicit Cloud/TLS/role setup, repeatable fixture reset, CSRF forms, and cleanup instructions.
Verified natively on Linux ARM64 against ClickHouse Managed Postgres 18.6, pg_clickhouse 0.10.0 and ClickHouse 26.6.1.2191: clean secret-free AOT build and four unit tests/29 assertions; live two-editor 303/409, rollback after the first update, retained escaped forms/Chromium CSRF, exact all-customer foreign/direct results, bounded parameterized query pushdown, restricted roles and real driver CA/hostname rejection, and real process restart. Revoked analytical SELECT produced sequential report failures while a subsequent operational save succeeded; restored reporting recovered on the same process. No CDC, dual writes, public authentication, cross-database atomicity or performance claim. Both owned Cloud fixtures are deleted with exact IDs verified absent; evidence/article remain local for review.