Hi Julian Hyde, you are right, I did try to parse 'myfield' as a SqlIdentifier. However, I am hitting the problem of subfield validation. Basically, 'myfield' will be parsed as a standalone SqlIdentifier, and in the validation process, it will try to fullyQualify the SqlIdentifier, which the validation scope won't be able to find 'myfield' as it's nested under a top level field.
The approach I was taking basically treat DOT similar to ITEM. In ITEM, you don't need to check the second operand as it's a literal. So the current implementation
will bypass checking if the subfield actually exist in the record.
Also, I think about extend SqlIdentifier(see CompoundIdentifier()) itself to support both ITEM and DOT. However, in that case, you can't support complex expression in the ITEM operand, e.g.
What's your recommendation? Thanks.