-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
PostgreSQL hex and binary numeric literals are not recognized correctly #4354
Comments
be-happy4
added a commit
to be-happy4/grammars-v4
that referenced
this issue
Dec 11, 2024
be-happy4
added a commit
to be-happy4/grammars-v4
that referenced
this issue
Dec 11, 2024
be-happy4
added a commit
to be-happy4/grammars-v4
that referenced
this issue
Dec 12, 2024
be-happy4
added a commit
to be-happy4/grammars-v4
that referenced
this issue
Dec 12, 2024
be-happy4
added a commit
to be-happy4/grammars-v4
that referenced
this issue
Dec 12, 2024
be-happy4
added a commit
to be-happy4/grammars-v4
that referenced
this issue
Dec 12, 2024
be-happy4
added a commit
to be-happy4/grammars-v4
that referenced
this issue
Dec 12, 2024
be-happy4
added a commit
to be-happy4/grammars-v4
that referenced
this issue
Dec 12, 2024
be-happy4
added a commit
to be-happy4/grammars-v4
that referenced
this issue
Dec 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
0x10
and0b10
should be recognized as ahex literal
and abinary literal
respectively. But they are0
and aidentifier
now, which is incorrect. Maybe010
should be aoctal literal
. But it seems to have been done right by accident.The text was updated successfully, but these errors were encountered: