Data-Intensive XQuery Debugging with Instant Replay.pdf

Data-Intensive XQuery Debugging with Instant Replay.pdf

  1. 1、本文档共6页,可阅读全部内容。
  2. 2、有哪些信誉好的足球投注网站(book118)网站文档一经付费(服务费),不意味着购买了该文档的版权,仅供个人/单位学习、研究之用,不得用于商业用途,未经授权,严禁复制、发行、汇编、翻译或者网络传播等,侵权必究。
  3. 3、本站所有内容均由合作方或网友上传,本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺!文档内容仅供研究参考,付费前请自行鉴别。如您付费,意味着您自己接受本站规则且自行承担风险,本站不退款、不进行额外附加服务;查看《如何避免下载的几个坑》。如果您已付费下载过本站文档,您可以点击 这里二次下载
  4. 4、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等,请点击“版权申诉”(推荐),也可以打举报电话:400-050-0827(电话支持时间:9:00-18:30)。
查看更多
Data-Intensive XQuery Debugging with Instant Replay

Data-Intensive XQuery Debugging with Instant Replay Torsten Grust Jan Rittinger Jens Teubner Technische Universita?t Mu?nchen Munich, Germany torsten.grust | jan.rittinger | jens.teubner@in.tum.de ABSTRACT We explore the design and implementation of Rover , a post- mortem debugger for XQuery. Rather than being based on the traditional breakpoint model, Rover acknowledges XQuery’s nature as a functional language: the debugger fol- lows a declarative debugging paradigm in which a user is enabled to observe the values of selected XQuery subexpres- sions. Rover has been designed to hook into Pathfinder , an XQuery compiler that emits relational algebra plans for eval- uation on commodity relational database back-ends. The debugger instruments the subject query with fn:trace() calls which, at query runtime, populate database tables with relational representations of XQuery item sequences. Thanks to Pathfinder ’s loop-lifting compilation strategy, a Rover trace (1) may span multiple XQuery for iteration scopes and (2) allows for interactive debugging sessions that can arbitrarily replay iterations in a unique forward/backward fashion. Since the query runtime as well as the debugger are database-supported, Rover is scalable and supports the observation of very data-intensive XQuery expressions. 1. DEBUGGING XQUERY Our own experience has taught us that authoring a mod- erately complex XQuery expression from scratch more often than not tends to yield queries which exhibit unexpected behavior. Such bugs may sometimes have obvious fixes, but at times they might only occur with specific input XML in- stances or are, generally, hard to track down. While we do not postulate that XQuery authoring is inherently prone to error, there are a number of language characteristics and intricacies that may turn into pitfalls. Consider that (1) much of the XQuery semantics is implicit and does not surface at the language level (e.g., existential quantifi- cation or casting), (2) expression e

文档评论(0)

l215322 + 关注
实名认证
内容提供者

该用户很懒,什么也没介绍

1亿VIP精品文档

相关文档