Update documentation around custom formatters. #2310
Closed
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
The example worked for me but since 99.9% of the existing project was using ? placeholders I tidied the Function example up to first check if the SQL statement used ? and then customised for that before checking if it should be named parameters. Also we have one SQL that seems to be using := assignment, I have added a condition for it to not effect that.
|
Thank you, but this is just an example made to be simple to understand. The idea is that users can write whatever they like for their use case and the example is simply to demonstrate how to use the API👍 |
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.
The example worked for me but since 99.9% of our existing project was using ? placeholders I tidied the Function example up to first check if the SQL statement used ? and then customised for that before checking if it should be named parameters. Also we have one SQL that seems to be using := assignment, I have added a condition for it to not effect that.