Repository navigation
Conversation
SQLClean 0.4.3 finds unused CTEs without deep-cloning each WITH query. Lint output is unchanged.
Contributor
Author
|
Superseded by the replacement pull request from |
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.
Why
SQLClean 0.4.3 makes SQLCLEAN005 (unused CTE) facts cheaper: it no longer deep-clones every query with a WITH clause. This is a small part of the default-Rules cold-compile cost and does not recover the regression tracked in #1289.
Changes
sqlcleanto the v0.4.3 release commitcf79656. The lockfile changes only thesqlcleanentry; its polyglot revision is unchanged.Verification
sqlclean0.4.3 reports the expected SQLCLEAN005 findings.