-
Notifications
You must be signed in to change notification settings - Fork 346
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DATAJDBC-357 - Introduce dialect support to render paginated queries. #125
Closed
Conversation
This file contains 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
This was referenced Mar 15, 2019
…roduce context hooks.
mp911de
force-pushed
the
issue/DATAJDBC-278
branch
from
March 27, 2019 12:18
cdb2dba
to
0323795
Compare
schauder
changed the title
DATAJDBC-278 - Introduce dialect support to render paginated queries.
DATAJDBC-357 - Introduce dialect support to render paginated queries.
Apr 9, 2019
schauder
pushed a commit
that referenced
this pull request
Apr 9, 2019
We now support Dialect abstractions to consider vendor-specific deviations in SQL query rendering. Dialects support right now: Feature flags for array support Limit and Offset handling The rendering is extended by considering rendering callback hook functions. Current dialects: Postgres SQL SQL Server (2012) MySQL Original pull request: #125
schauder
pushed a commit
that referenced
this pull request
Apr 9, 2019
We now support Dialect abstractions to consider vendor-specific deviations in SQL query rendering. Dialects support right now: Feature flags for array support Limit and Offset handling The rendering is extended by considering rendering callback hook functions. Current dialects: Postgres SQL SQL Server (2012) MySQL Original pull request: #125.
schauder
added a commit
that referenced
this pull request
Apr 9, 2019
Implemented workaround for MySql not supporting offset without Limit. Using `SELECT 1` as dummy order by since it is documented to be optimized away. Renamed tests to match the project standard. See also: - https://stackoverflow.com/a/44106422 - https://stackoverflow.com/a/271650 Original pull request: #125.
Polished and merged. |
This was referenced Dec 31, 2020
mp911de
added a commit
that referenced
this pull request
Feb 21, 2022
We now reuse the existing Dialect infrastructure provided by Spring Data Relational to enhance it for R2DBC specifics such as bind markers. Original pull request: #125.
mp911de
pushed a commit
that referenced
this pull request
Feb 21, 2022
Minor changes to documentation in order to avoid <literal code>``s constructs as recommended by our style guide. Original pull request: #125.
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.
We now support
Dialect
abstractions to consider vendor-specific deviations in SQL query rendering. Dialects support right now:Limit
andOffset
handlingThe rendering is extended by considering rendering callback hook functions.
Current dialects: