Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support INTERSECT query term #112

Open
jaypipes opened this issue May 26, 2018 · 0 comments
Open

Support INTERSECT query term #112

jaypipes opened this issue May 26, 2018 · 0 comments
Labels
DML
Milestone
0.2

Comments

@jaypipes
Copy link
Owner 

<non-join query term> ::=
    <non-join query primary>
    | <query term> INTERSECT
    [ ALL ] [ <corresponding spec> ] <query primary>
@jaypipes jaypipes added the DML label May 26, 2018
@jaypipes jaypipes added this to the 0.2 milestone May 26, 2018
jaypipes added a commit that referenced this issue May 26, 2018
@jaypipes
Break out parsers for query expression components
e7ede24 
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
jaypipes added a commit that referenced this issue May 26, 2018
@jaypipes
parse query_specification and table_expression
6374749 
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
DML
Projects
None yet
Milestone
0.2
Development

No branches or pull requests
1 participant
@jaypipes