Initial unicode support for identifiers and whitespace from SQL 2016 spec #41
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
|
|
Open
kaikalur
force-pushed
the
unicode-support
branch
5 times, most recently
from
55fc66f to
b091c7e
Compare
kaikalur
force-pushed
the
unicode-support
branch
4 times, most recently
from
4997a55 to
e9f30c0
Compare
kaikalur
changed the title
Summary: Test Plan: Added a test Reviewers: Subscribers: Tasks: Tags:
kaikalur
force-pushed
the
unicode-support
branch
from
e9f30c0 to
7318638
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
SQL 2016 spec allows for identifers to be full unicode. So we fixed the grammar based on that definition of
<identifier start> and <identifier extend>