Skip to content

Conversation

@vsai12
Copy link
Contributor

@vsai12 vsai12 commented Jan 13, 2026

Summary

  • Add new tokens from the grammar sync to the regular_id rule so they can be used as identifiers
  • Tokens added: ITEMS, BYTES, LINES, RECORDS, FIELD, MASK, NEWLINE_, CHARSETFORM, CHARSETID, DURATION, ENABLED, MAXLEN, ERROR_CODE, ERROR_INDEX, EXTEND, NOEXTEND, NOSCALE, NOSHARD, SHARD, POLYMORPHIC

Problem

These tokens were added to the lexer in the grammar sync (#47) but were not added to regular_id, causing them to be treated as reserved keywords that cannot be used as identifiers.

For example, CREATE TABLE ITEMS (ID NUMBER PRIMARY KEY) fails to parse because ITEMS is tokenized but not allowed as an identifier.

Test plan

  • Parser tests pass (make test in plsql/)
  • Bytebase integration tests pass with updated parser

🤖 Generated with Claude Code

Add new tokens from the grammar sync to the regular_id rule so they
can be used as identifiers:
- ITEMS, BYTES, LINES, RECORDS, FIELD, MASK, NEWLINE_
- CHARSETFORM, CHARSETID, DURATION, ENABLED, MAXLEN
- ERROR_CODE, ERROR_INDEX
- EXTEND, NOEXTEND, NOSCALE, NOSHARD, SHARD, POLYMORPHIC

These tokens were added to the lexer in the grammar sync but were
not added to regular_id, causing them to be treated as reserved
keywords that cannot be used as identifiers.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@vsai12 vsai12 merged commit f93143b into main Jan 13, 2026
5 checks passed
@vsai12 vsai12 deleted the fix/plsql-regular-id-tokens branch January 13, 2026 04:06
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.

2 participants