2007 IEEE 23rd International Conference on Data Engineering 2007
DOI: 10.1109/icde.2007.367850
|View full text |Cite
|
Sign up to set email alerts
|

Unnesting Scalar SQL Queries in the Presence of Disjunction

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
6
0

Year Published

2007
2007
2021
2021

Publication Types

Select...
4
2
1

Relationship

1
6

Authors

Journals

citations
Cited by 9 publications
(6 citation statements)
references
References 15 publications
0
6
0
Order By: Relevance
“…In our approach, both no and all can be computed by applying the algorithms in [32] or [27] to the result of the join, or (as before) by grouping such result by the parameter ok and applying a count aggregate on each group: the result of the count is then used to filter the appropriate groups. The only caveat is that for no, outerjoin must be used, similar to unnesting [6]. We stress that either approach can handle more complex queries where several quantifiers are used (either nested within each other or at the same level).…”
Section: Computing Generalised Quantificationmentioning
confidence: 98%
See 1 more Smart Citation
“…In our approach, both no and all can be computed by applying the algorithms in [32] or [27] to the result of the join, or (as before) by grouping such result by the parameter ok and applying a count aggregate on each group: the result of the count is then used to filter the appropriate groups. The only caveat is that for no, outerjoin must be used, similar to unnesting [6]. We stress that either approach can handle more complex queries where several quantifiers are used (either nested within each other or at the same level).…”
Section: Computing Generalised Quantificationmentioning
confidence: 98%
“…Thus, the first subquery must be understood as if it had a correlation on.orderkey: for the purposes of evaluating the SOME operator, it lists all partkeys associated with a given orderkey. 6 This set is compared with that of the second subquery: if the intersection is not empty, then the orderkey qualifies for the answer. In other words, this query could be written in a more standard manner as follows:…”
Section: Using Gqs In Query Languagesmentioning
confidence: 99%
“…The paper [12] suggests an interesting way of avoiding the duplication of relation R by using a bypass operator. The query is converted into a DAG where the bypass operator dispatches the rows to the branches of the DAG and a union-all at the top combines them together again.…”
Section: Complex Correlationmentioning
confidence: 99%
“…They extend the relational algebra with the so-called apply operator that is used to algebraically represent nested queries in the WHERE clause. Both Brantner et al [3] and Neumann and Kemper [17] extend the relational algebra with new operators to algebraically represent subquery unnestings. In the latter case, these operators use sideways information passing to execute nested queries more efficiently.…”
Section: Related Workmentioning
confidence: 99%
“…These techniques either work at the level of SQL [14,20], define new operators [3,9] and algebras [4] that are specifically targeted at nested queries, or build on entirely different formalisms, e.g., comprehension calculus [8,12,13]. We argue that these approaches all have drawbacks that have limited their adoption in database systems.…”
Section: Introductionmentioning
confidence: 99%