ACM SIGMOD Record
System RX: one part relational, one part XML
Proceedings of the 2005 ACM SIGMOD international conference on Management of data
Managing structure in bits & pieces: the killer use case for XML
Proceedings of the 2005 ACM SIGMOD international conference on Management of data
XML and relational database management systems: the inside story
Proceedings of the 2005 ACM SIGMOD international conference on Management of data
DB2/XML: designing for evolution
Proceedings of the 2005 ACM SIGMOD international conference on Management of data
Towards an enterprise XML architecture
Proceedings of the 2005 ACM SIGMOD international conference on Management of data
Native XML support in DB2 universal database
VLDB '05 Proceedings of the 31st international conference on Very large data bases
Integration of SQL and XQuery in IBM DB2
IBM Systems Journal
DB2 goes hybrid: integratng native XML and XQuery with relational data and SQL
IBM Systems Journal
Cost-based optimization in DB2 XML
IBM Systems Journal
A framework for using materialized XPath views in XML query processing
VLDB '04 Proceedings of the Thirtieth international conference on Very large data bases - Volume 30
Usage-driven storage structures for native XML databases
IDEAS '08 Proceedings of the 2008 international symposium on Database engineering & applications
Recommending XML physical designs for XML databases
The VLDB Journal — The International Journal on Very Large Data Bases
Hi-index | 0.00 |
XQuery and SQL/XML are powerful new languages for querying XML data. However, they contain a number of stumbling blocks that users need to be aware of to get the expected results and performance. For example, certain language features make it hard if not impossible to exploit XML indexes.The major database vendors provide XQuery and SQL/XML support in their current or upcoming product releases. In this paper, we identify common pitfalls gleaned from the experiences of early adopters of this functionality. We illustrate these pitfalls through concrete examples, explain the unexpected query behavior, and show alternative formulations of the queries that behave and perform as anticipated. As results we provide guidelines for XQuery and SQL/XML users, feedback on the language standards, and food for thought for emerging languages and APIs.