Open
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.
This PR contains the following updates:
==0.3.1→==0.5.5Release Notes
andialbrecht/sqlparse (sqlparse)
v0.5.5Compare Source
Bug Fixes
when grouping limits are exceeded (issue827).
v0.5.4Compare Source
Enhancements
for PEP 561 compliance, enabling type checking with mypy and other tools
(issue756).
to automatically format SQL files. The CLI now supports multiple files and
an
--in-placeflag for in-place editing (issue537).ATTACHandDETACHto PostgreSQL keywords (pr808).INTERSECTto close keywords in WHERE clause (pr820).REGEXP BINARYcomparison operator (pr817).Bug Fixes
very large lists of tuples. This enhances the existing recursion protections
with configurable limits for token processing to prevent DoS through
algorithmic complexity attacks. The new limits (MAX_GROUPING_DEPTH=100,
MAX_GROUPING_TOKENS=10000) can be adjusted or disabled (by setting to None)
if needed for legitimate large SQL statements.
comments (issue801, pr803 by stropysh).
blocks (issue812).
v0.5.3Compare Source
Bug Fixes
service attack (DOS) due to recursion errors for deeply nested statements.
Brought up and fixed by @living180. Thanks a lot!
v0.5.2Compare Source
Bug Fixes
v0.5.1Compare Source
Enhancements
a more compact output by avoiding some line breaks (issue783).
Bug Fixes
whitespace (issue772).
Note: In some cases you might want to add
strip_whitespace=Truewhere youpreviously used just
strip_comments=True.strip_commentsdid some of thework that
strip_whitespaceshould do.within a BEGIN block (issue784).
NULLS LAST (issue532).
v0.5.0Compare Source
Notable Changes
error for deeply nested statements. Instead of recursion error a generic
SQLParseError is raised. See the security advisory for details:
GHSA-2m57-hf25-phgg
The vulnerability was discovered by @uriyay-jfrog. Thanks for reporting!
Enhancements
Some database backends love statements without semicolon (issue742).
Bug Fixes
by josuc1, thanks for bringing this up!).
Other
v0.4.4Compare Source
Notable Changes
parser where a regular expression vulnerable to ReDOS (Regular
Expression Denial of Service) was used. See the security advisory
for details: GHSA-rrm6-wvj7-cwh2
The vulnerability was discovered by @erik-krogh from GitHub
Security Lab (GHSL). Thanks for reporting!
Bug Fixes
The primary expectation is that IN is treated as a keyword and not as a
comparison operator. That also follows the definition of reserved keywords
for the major SQL syntax definitions.
Other
v0.4.3Compare Source
Enhancements
Bug Fixes
Other
v0.4.2Compare Source
Notable Changes
strip comments filter. In this filter a regular expression that was
vulnerable to ReDOS (Regular Expression Denial of Service) was
used. See the security advisory for details: GHSA-p5w8-wqhj-9hhf
The vulnerability was discovered by @erik-krogh and @yoff from
GitHub Security Lab (GHSL). Thanks for reporting!
Enhancements
Bug Fixes
v0.4.1Compare Source
Bug Fixes
v0.4.0Compare Source
Notable Changes
required.
statements anymore. Code that ignored the last element from
sqlparse.split() should be updated accordingly since that function
now doesn't return an empty string as the last element in some
cases (issue496).
Enhancements
Bug Fixes
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.