Fix WHERE clause parsing to support property access
🐛 BUG FIX:
- Add property access parsing (a.name) to primary_expression parser
- WHERE clauses with property comparisons now parse correctly
- Support for compound WHERE conditions with AND/OR operators
✅ IMPROVEMENTS:
- Can now parse: WHERE a.name = 'Alice'
- Can now parse: WHERE a.name = 'Alice' AND b.name = 'Bob'
- Add test coverage for WHERE clause parsing
🚧 KNOWN ISSUE:
- WHERE clauses parse correctly but don't filter results yet
- Execution logic needs to be implemented to actually apply WHERE filters
- This commit only fixes the parsing error, not the execution
BEFORE:
Error: Query parsing failed: Unexpected tokens after query: [Dot, Identifier("name"), ...]
AFTER:
Query parses successfully (though filtering not yet implemented)
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>