julianhyde commented on pull request #2271: URL: https://github.com/apache/calcite/pull/2271#issuecomment-730680731
Let's just suppose for a minute that Oracle's SUBSTR function had the same semantics as standard SUBSTRING, just different syntax. Then it is not a goal to keep it intact through Calcite's planning process. Calcite's philosophy is to convert to a minimal language. That creates opportunities for simplification/optimization. If Oracle is the target, then we should translate SUBSTRING back to SUBSTR when we generate Oracle SQL. But it is not necessarily the target. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
