Skip to content

Conversation

@llali
Copy link
Member

@llali llali commented Sep 17, 2025

Description

Fixes #160
In addition, go through the checklist below and check each item as you validate it is either handled or not applicable to this change.

Code Changes

@clement911
Copy link

Note that fixing this bug will hopefully fix #28 at the same time, as I believe it is caused by the same root issue.

@llali
Copy link
Member Author

llali commented Sep 19, 2025

Note that fixing this bug will hopefully fix #28 at the same time, as I believe it is caused by the same root issue.

I don't think so but I'll double check

++insideIIf;
}
// if identifier is REGEXP_LIKE
else if(NextTokenMatches(CodeGenerationSupporter.RegexpLike))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be more appropriate to add it to TSql170ParserBaseInternal or whichever version introduces this syntax?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

probably yes but it's fine since we added other syntaxes here as well. I can rename the function later

@llali llali merged commit cd170a8 into main Sep 22, 2025
8 checks passed
@clement911
Copy link

@llali could you release this fix so that we can test it out?

@llali
Copy link
Member Author

llali commented Oct 21, 2025

@clement911 this should be in 170.128.0

@clement911
Copy link

Ah yes thank you @llali , confirming it works now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Parse error when using REGEXP_LIKE

5 participants