F# Type Provider for LQL with Compile-Time Validation#15
Merged
MelbourneDeveloper merged 12 commits intomainfrom Jan 5, 2026
Merged
F# Type Provider for LQL with Compile-Time Validation#15MelbourneDeveloper merged 12 commits intomainfrom
MelbourneDeveloper merged 12 commits intomainfrom
Conversation
MelbourneDeveloper
added a commit
that referenced
this pull request
Apr 7, 2026
#12 op method names use the literal table.Name (e.g. 'Insertgk_userAsync') instead of PascalCasing it. The SQLite.Cli emits the literal name and consumer call sites depend on it. #13 query method parameters use the SQL @param name verbatim ('resource_id') instead of camelCasing it. Consumer call sites that use named arguments (CheckResourceGrantAsync(resource_id: ...)) broke when the codegen renamed them. #14 byte[] (Postgres bytea) columns are now always emitted as 'byte[]?' even when the schema marks the column NOT NULL. Postgres bytea metadata is unreliable about nullability and the reader can return null at runtime, causing CS8604 warnings on non-nullable byte[] receivers. #15 query record types are non-positional now: public record Foo { public string id { get; init; } public string? name { get; init; } } instead of the positional 'public sealed record Foo(string id, ...)'. Per-property nullability comes from the column metadata. The ReadFoo() reader uses object-initializer syntax 'new() { ... }' to match the new shape. Restores parity with the old SQLite.Cli output. Bumps Postgres.Cli to 0.2.4-beta.
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.
F# Type Provider for LQL with Compile-Time Validation
TLDR;
Adds an F# type provider that validates LQL queries at compile time, converting them to SQL. Invalid LQL syntax causes compilation errors rather than runtime failures.
Brief Details
Lql.LqlCommand<"query">) that parses LQL at compile time, validates syntax, and generates SQLQuery(original LQL) andSql(generated SQL) static propertieslql-fsharp-typeprovider-testsruns F# type provider tests on LQL changes.lqlquery filesHow Do The Tests Prove This Works?
TypeProviderCompileTimeValidationTests: VerifyQueryandSqlproperties are generated correctlyTypeProviderFilterTests: Confirm filter expressions generate properWHEREclauses withAND/ORTypeProviderJoinTests: ValidateJOIN,LEFT JOIN, and multi-table joins produce correct SQLTypeProviderAggregationTests: TestGROUP BY,SUM,AVG,COUNT, andHAVINGclausesTypeProviderE2EExecutionTests: Execute generated SQL against real SQLite database, verify row counts and dataTypeProviderRealWorldScenarioTests: End-to-end scenarios querying customers, filtering users, joining orders