Introduce a NativeParametersRendering service to directly render PostgreSQL-compatible SELECT statements #1488
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
…greSQL-compatible SELECT statements This avoids some post-processing of the SQL generated by ORM core; it takes care of the PostgreSQL specific parameters format; not applicable yet for mutation operations.
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.
It turns out we can't get rid of the
Parametersapproach to avoid post-processing of SQL statements, but there's some progress.This avoids some post-processing of the SQL generated by ORM core; it takes care of the PostgreSQL specific parameters format; not applicable yet for mutation operations.