Conversation
patricebender
approved these changes
Mar 13, 2026
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.
This PR adds a long requested feature to produce human readable statements. With the combined complexity of real
cqnqueries and the restrictions thatsqlstatements have. The resulting realsqlstatements produce angst and/or confusion in application developers. Therefor the introduction ofpqlwhich is a pseudo query language that looks likesql, but ignores some of the major restrictionssqlenforces. The primary restriction isscalar sub selectsinpqlthis is ignored and allowsexpandqueries to be rendered in its principle form. Removing a large amount of visual clutter that preventsqlstatements from being easily readable.Possible names for
pql: