-
Notifications
You must be signed in to change notification settings - Fork 264
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
feat: Explain command support #444
Conversation
Can you @gaurav274 give a proofread of current implementation from parser to statement before I go to the optimizer? As we discussed, the explainable statement/operator/plan will always be embedded as an attribute in the current design. |
@@ -75,6 +76,10 @@ def _bind_abstract_expr(self, node: AbstractExpression): | |||
for child in node.children: | |||
self.bind(child) | |||
|
|||
@bind.register(ExplainStatement) | |||
def _bind_explain_statement(self, node: ExplainStatement): | |||
self.bind(node.explainable_stmt) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right now, bind will create catalog entries. @gaurav274 This can be a consideration to move catalog operations to executors.
I think the idea of the current implementation works. |
Add
EXPLAIN
support in the system.