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.

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

make a query execution traverser #36

Closed
andykais opened this issue Sep 11, 2019 · 0 comments · Fixed by #33
Closed

make a query execution traverser #36

andykais opened this issue Sep 11, 2019 · 0 comments · Fixed by #33

Comments

@andykais
Copy link
Owner

the ordered scraper query is fairly complex, and debugging it can be difficult. An idea springs to mind where we add some debug blocks to the scraper and then can choose to output the query plan. Things in the debug blocks:

  • the ordering info (recurseDepth, horizontalIndex, etc.)
  • not the WHERE recurseDepth = {{ lowestDepth }}

somehow we plug this in. Maybe a flag on params and a wrapper on the query statement that consumes the output, then plays it back at 1 second intervals to show how the data moves at each step in the recursion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant