The parser takes SQL queries and creates a tree that is then
optimized and executed by the Minibase planner.
Ideally, type checking of attributes / relations should be done
here, but since the catalog structure was changing while this was
being developed, type checking is done by the optimizer.
Bugs in the Parser
- Inserts and deletes are not supported through the parser.
- It can't handle: VAL op attrName. However, it can do this=> attrName op VAL>
Back to the Components Page
Back to the Minibase Home Page