Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Expr::XmlConcat(Vec<Expr>)variant withDisplayandSpannedimplementations for PostgreSQL'sXMLCONCAT(xml[, ...])functionmaybe_parse_xml_functiondispatcher in the parser, hooked at the top ofparse_function, which routes XML function names to dedicated AST nodes on dialects wheresupports_xml_expressions()is truexmlconcat(...)on PostgreSQL and Generic dialects takes the new path — all other dialects and qualified/quoted names fall through to the normal function-call parserThis is the second PR in a chain splitting #2252 (XML function support) into reviewable units. Builds on #2299 which introduced the
supports_xml_expressions()dialect method.