fix(sqlite): Correctly skip unknown statements #3239
Merged
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
Without updating loc, the unknown statement would be included in the text of the next query.
lisitsky
pushed a commit
to lisitsky/sqlc
that referenced
this pull request
Jun 21, 2024
* fix(sqlite): Correctly skip unknown statements Without updating loc, the unknown statement would be included in the text of the next query. * Pick sqlc-gen-typescript to a release
alfonsodev
pushed a commit
to ExponentiaTeam/sqlc
that referenced
this pull request
Oct 13, 2025
* fix(sqlite): Correctly skip unknown statements Without updating loc, the unknown statement would be included in the text of the next query. * Pick sqlc-gen-typescript to a release
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.
Without updating loc, the unknown statement would be included in the text of the next query.
This will address the invalid query part of #3237