Fix sequence name quoting #409
Merged
Conversation
This file contains 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
Taepper
force-pushed
the
fix-sequenceNameQuoting
branch
2 times, most recently
from
8d8d5d7
to
23ca0f0
Compare
…ith a number leads to parser errors
Taepper
force-pushed
the
fix-sequenceNameQuoting
branch
from
23ca0f0
to
cdf4b46
Compare
|
Works, tested and bug no longer occurs |
|
resolves #408 |
corneliusroemer
approved these changes
May 7, 2024
chaoran-chen
approved these changes
May 7, 2024
This was referenced May 8, 2024
Merged
2 tasks
This was referenced Sep 12, 2024
Merged
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.
fix: quoting {} in "x.{}" SQL struct accesses, as a string starting w…
…ith a number leads to parser errors