-
Notifications
You must be signed in to change notification settings - Fork 4
fix: Revert sqlparse parsing limits to pre-0.5.4 defaults #77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
m1so
merged 2 commits into
main
from
michalbaumgartner/blu-5817-revert-sqlparse-parsing-limits-to-pre-054-defaults
Mar 17, 2026
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,52 @@ | ||
| import pytest | ||
| import sqlparse.engine.grouping | ||
| from sqlparse.exceptions import SQLParseError | ||
|
|
||
| from deepnote_toolkit.sql.sql_utils import ( | ||
| configure_sqlparse_limits, | ||
| is_single_select_query, | ||
| reset_sqlparse_limits, | ||
| ) | ||
|
|
||
|
|
||
| class TestSqlparseLimits: | ||
| @pytest.fixture(autouse=True) | ||
| def disable_sqlparse_limits(self): | ||
| """Ensure every test starts and ends with limits disabled.""" | ||
| configure_sqlparse_limits() | ||
| yield | ||
| configure_sqlparse_limits() | ||
|
|
||
| @staticmethod | ||
| def _build_large_select(num_columns: int = 5000) -> str: | ||
| """Build a SELECT with enough columns to exceed the default 10,000 token limit.""" | ||
| columns = ", ".join(f"column_{i}" for i in range(num_columns)) | ||
| return f"SELECT {columns} FROM some_table" | ||
|
|
||
| def test_disables_limits_by_default(self): | ||
| assert sqlparse.engine.grouping.MAX_GROUPING_TOKENS is None | ||
| assert sqlparse.engine.grouping.MAX_GROUPING_DEPTH is None | ||
|
|
||
| def test_sets_custom_values(self): | ||
| expected_tokens = 50_000 | ||
| expected_depth = 200 | ||
| configure_sqlparse_limits( | ||
| max_grouping_tokens=expected_tokens, max_grouping_depth=expected_depth | ||
| ) | ||
| assert sqlparse.engine.grouping.MAX_GROUPING_TOKENS == expected_tokens | ||
| assert sqlparse.engine.grouping.MAX_GROUPING_DEPTH == expected_depth | ||
|
|
||
| def test_restores_builtin_defaults(self): | ||
| reset_sqlparse_limits() | ||
| assert sqlparse.engine.grouping.MAX_GROUPING_TOKENS == 10_000 | ||
| assert sqlparse.engine.grouping.MAX_GROUPING_DEPTH == 100 | ||
|
|
||
| def test_large_query_parses_with_limits_disabled(self): | ||
| large_query = self._build_large_select() | ||
| assert is_single_select_query(large_query) is True | ||
|
|
||
| def test_large_query_fails_with_default_limits(self): | ||
| reset_sqlparse_limits() | ||
| large_query = self._build_large_select() | ||
| with pytest.raises(SQLParseError): | ||
| is_single_select_query(large_query) | ||
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.