2005
DOI: 10.1016/j.datak.2004.12.003
|View full text |Cite
|
Sign up to set email alerts
|

Accelerating queries by pruning XML documents

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
17
0

Year Published

2007
2007
2012
2012

Publication Types

Select...
4
2

Relationship

0
6

Authors

Journals

citations
Cited by 9 publications
(17 citation statements)
references
References 21 publications
0
17
0
Order By: Relevance
“…Section VI then introduces a new runtime XML projection technique, which we use to generate messages that conserve all needed structural relationships between transferred XML nodes, and thus allow even more freedom in query decomposition. As a runtime technique, it is able to prune XML data much more than previously described compile-time projections [3], [5], [15]. An evaluation of the performance benefits of our techniques is given in Section VII.…”
Section: Introductionmentioning
confidence: 91%
See 1 more Smart Citation
“…Section VI then introduces a new runtime XML projection technique, which we use to generate messages that conserve all needed structural relationships between transferred XML nodes, and thus allow even more freedom in query decomposition. As a runtime technique, it is able to prune XML data much more than previously described compile-time projections [3], [5], [15]. An evaluation of the performance benefits of our techniques is given in Section VII.…”
Section: Introductionmentioning
confidence: 91%
“…[5] introduces a precise XML pruning technique for a subset of XQUERY FLWOR expressions, based on the apriori knowledge of a data guide for underlying XML data. However, it does not handle XPATH predicates, backward axes and XQUERY-like languages.…”
Section: Evaluation In Monetdb/xquerymentioning
confidence: 99%
“…XML projection [21] drastically reduces the size of the data model representation using compile-time query characterization. Bressan et al [5] introduces a precise XML pruning technique for a subset of XQUERY FLWOR expressions, based on the a priori knowledge of a data guide for underlying XML data. However, it does not handle XPATH predicates, backward axes, and XQUERYlike languages.…”
Section: Related Workmentioning
confidence: 99%
“…As mentioned in Section 4, in the definition of Dðv x Þ, 5 we use a wildcard URIÃ if the document name is an expression. All paths start with doc(uri::v i ), thus, they identify both document URI and the vertex v i where it is loaded.…”
Section: Extending Projected Xmlmentioning
confidence: 99%
See 1 more Smart Citation