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.
Scientific notation with an explicit positive exponent is split into separate tokens: formatting
SELECT 1e+3*2withuse_space_around_operators=TrueproducesSELECT 1e + 3 * 2, changing the SQL.Allow either sign in the exponent part of the existing numeric-literal rule. Parsing tests cover uppercase/lowercase exponent markers, integer/decimal mantissas, and negative values; formatting tests verify that the exponent stays intact while the multiplication operator receives spaces.
ruff check sqlparse/andgit diff --checkpassed.Prepared with OpenAI Codex assistance for implementation, tests, and review.