You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In supporting UNION/INTERSECT/EXCEPT, we need to segregate the parsing
of query expression components from both table references and the
select_statement_t.
This patch adds specific parsers for the following query expression
components:
- <non_join_query_expression>
- <non_join_query_term>
- <non_join_query_primary>
- <query_term>
- <query_primary>
- <joined_table>
- <query_expression>
The parsing of <query_specification> (which is basically the SELECT
statement) is left for a followup patch, since that will need to reshape
the parse_select() function substantially.
Issue #78
Issue #111
Issue #112
The remaining pieces of the separate query component parsers were the
parsing of the query_specification_t and table_expression_t.
Next step is to convert parse_select() into a smaller parser that calles
parse_query_specification() and checks terminal symbols that can come
after a SELECT statement.
Issue #78
Issue #111
Issue #112
The text was updated successfully, but these errors were encountered: