Liangda-w commented on pull request #10052: URL: https://github.com/apache/shardingsphere/pull/10052#issuecomment-821201358
> @wgy8283335 if use `(PCTFREE NUMBER_ | PCTUSED NUMBER_ | INITRANS NUMBER_ | storageClause)+` will get an error. I think we can use `(PCTFREE NUMBER_ | PCTUSED NUMBER_ | INITRANS NUMBER_ | storageClause) (PCTFREE NUMBER_ | PCTUSED NUMBER_ | INITRANS NUMBER_ | storageClause)*` to resolve to this error. @Liangda-w do you think so. Hi @zhujunxxxxx, thank you for the suggestion:) I think my expression before might not be so clear. Actually `(PCTFREE NUMBER_ | PCTUSED NUMBER_ | INITRANS NUMBER_ | storageClause)*` will causes this error `rule XXX contains an optional block with at least one alternative that can match an empty string` for the rule `oidIndexClause` and `indexPartitionDesc`, which in my opinion couldn't be avoided due to their definitions. Currently `(PCTFREE NUMBER_ | PCTUSED NUMBER_ | INITRANS NUMBER_ | storageClause)+` is fine, but it's not so suitable because `physicalAttributesClause` also allows an empty string. @tristaZero do you have any suggestions? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
