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

[v1] Support operator node within AST #1478

Closed
alancai98 opened this issue May 30, 2024 · 0 comments · Fixed by #1499
Closed

[v1] Support operator node within AST #1478

alancai98 opened this issue May 30, 2024 · 0 comments · Fixed by #1499

Comments

@alancai98
Copy link
Member

Similar to #1460, we can consider simplifying our AST representation of many unary and binary operators into a dedicated operator node. This can allow us to eventually support custom operators similar to what postgresql allows users to define -- https://www.postgresql.org/docs/current/sql-createoperator.html.

This issue does not track actually plumbing through operator resolution into the SPI and catalog but gets rid of some AST nodes that can be modeled with the operator node.

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

Successfully merging a pull request may close this issue.

1 participant