Fix PostgreSQL constraint migrations and refresh LQL docs#52
Merged
MelbourneDeveloper merged 7 commits intomainfrom May 7, 2026
Merged
Fix PostgreSQL constraint migrations and refresh LQL docs#52MelbourneDeveloper merged 7 commits intomainfrom
MelbourneDeveloper merged 7 commits intomainfrom
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.
TLDR
Fix PostgreSQL migration constraint handling, add LQL
IN (...)predicate support, and refresh the LQL documentation site/deploy shape.What Was Added?
.agents/skills/*skill definitions and converted.claude/skills/*files to pointers.SchemaConstraintNamesplus PostgreSQL migration tests for named column check constraints and constraint-backed unique index drops.What Was Changed or Deleted?
in (...)membership predicates, used by function body LQL/RLS predicate flows./playground/, and uploads the Eleventy_siteartifact.in (...), named column check constraints, unique constraint inspection, and constraint-backed index drops.Related issues: #48, #49, #50, #51.
How Do The Automated Tests Prove It Works?
make cicompleted with exit code 0 locally during PR preparation.PostgresColumnCheckConstraintTests.ApplyYaml_WhenColumnCheckConstraintHasName_CreatesNamedPostgresConstraintsproves named YAML column checks materialize as PostgreSQL constraints and are idempotent after inspection.PostgresDropConstraintBackedIndexTests.DropIndex_WhenIndexBacksUniqueConstraint_DropsConstraintproves destructive unique removal drops the owning PostgreSQL constraint instead of failing onDROP INDEX.PostgresDropConstraintBackedIndexTests.Calculate_WhenUniqueConstraintSchemaConverged_DoesNotDropBackingIndexproves inspected unique constraints do not cause false destructive drops.TranslatePostgresBody_ExistsPipelineWithInList_EmitsInPredicateproves LQL body predicates emitIN (...)SQL.InvalidCharacter_ShouldReturnLexerErrorproves lexer errors surface as structured LQL errors with positions.Spec / Doc Changes
docs/specs/lql-spec.mdforin (...)predicate support.docs/specs/migration-spec.mdfor named column check constraints, PostgreSQL unique constraint inspection, and constraint-backed index drops.Breaking Changes