-
Notifications
You must be signed in to change notification settings - Fork 42
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
Upper case "CREATE" in column name ends table parse #94
Comments
Looks like your tokenizer is misidentifying keywords even when they are no separated by white space. |
@n2ygk no, ptoblem not in tokenizer, lol, problem in changes that I did in 0.22.0 version to get possible parse statements without ; or GO. I will fix it tomorrow and release the patch version. thanks for catching this. Very stupid issue )) I set jus ok, if line started with CREATE then it's new statement ))) looks like it was monkey in my head at that moment. I will change it to normal regular expression)) to avoid such cases |
Haha so it was my fault :-)
…On Tue, Nov 16, 2021 at 3:21 PM Iuliia Volkova ***@***.***> wrote:
@n2ygk <https://github.com/n2ygk> no, ptoblem not in tokenizer, lol,
problem in changes that I did in 0.22.0 version to get possible parse
statements without ; or GO. I will fix it tomorrow and release the patch
version. thanks for catching this
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#94 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABBHS52OZX4ILERIL7ABHFLUMK4M5ANCNFSM5IFFIBZQ>
.
|
@n2ygk Alan, I will close the issue - check my comment in PR) it was already released at the morning |
Describe the bug
It looks like you are seeing CREATE and breaking the table DDL parse...
To Reproduce
t1.sql:
t2.sql:
vs:
Expected behavior
A capitalized substring field name that is CREATE shouldn't break the parser.
The text was updated successfully, but these errors were encountered: