Document driver-specific function transforms - #19566
Merged
Merged
Conversation
LordSimal
approved these changes
Jul 26, 2026
Contributor
Author
|
@LordSimal Can I bug you to merge 5.x into 5.next so I can work on a change that would update this? |
Member
|
Sorry, i was on holiday since friday, so i didn't see your message. |
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
3 participants
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.
FunctionsBuilder implies a call to the specific sql function but it hides many driver-specific transforms. We should document these so users are aware of support when a specific function isn't supported and show when legacy sql is still being generated.
It's currently very difficult to discover as a user.