-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Implement class-based DTO projections for Fluent API #2327
Labels
theme: projections
Refinements around DTO and interface projections
type: enhancement
A general enhancement
Milestone
Comments
gregturn
added a commit
that referenced
this issue
Oct 7, 2021
Add support for both QueryByExampleExecutor and QuerydslPredicateExecutor. This is used in SimpleJpaRepository and QuerydslJpaPredicateExecutor, resulting in various test cases proving support by both examples and Querydsl predicates. NOTE: Class-based DTOs are NOT supported yet. Closes #2294. Related: #2327.
mp911de
added
the
theme: projections
Refinements around DTO and interface projections
label
Aug 13, 2024
This was referenced Nov 4, 2024
mp911de
added a commit
that referenced
this issue
Dec 3, 2024
Also, interface-based projections now use Tuple queries to consistently use tuple-based queries. Closes #2327
mp911de
pushed a commit
that referenced
this issue
Dec 3, 2024
There's a difference in what the query needs to look like using dto vs. interface projections where the former does not allow column aliases and the latter requires them. See #2327
mp911de
added a commit
that referenced
this issue
Dec 3, 2024
Simplify Querydsl templates retrieva and String query caching. Update documentation. Skip selection list rewriting if the returned type is an interface. Encapsulate rewrite information for Query. Reformat code. See #2327
christophstrobl
pushed a commit
that referenced
this issue
Dec 5, 2024
Also, interface-based projections now use Tuple queries to consistently use tuple-based queries. Closes #2327
christophstrobl
pushed a commit
that referenced
this issue
Dec 5, 2024
Refactor code duplications. See #2327
christophstrobl
added a commit
that referenced
this issue
Dec 5, 2024
There's a difference in what the query needs to look like using dto vs. interface projections where the former does not allow column aliases and the latter requires them. See #2327
christophstrobl
pushed a commit
that referenced
this issue
Dec 5, 2024
Simplify Querydsl templates retrieva and String query caching. Update documentation. Skip selection list rewriting if the returned type is an interface. Encapsulate rewrite information for Query. Reformat code. See #2327
mp911de
changed the title
Implement class-based DTOs for Fluent API
Implement class-based DTO projections for Fluent API
Dec 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
theme: projections
Refinements around DTO and interface projections
type: enhancement
A general enhancement
#2294 introduced the Fluent API. However, scheduling issues prevented us from implementing class-based DTOs.
As part of that development effort, the following chunk of code from
FetchableFluentQueryByExample
was withdrawn since it isn't relevant to everything.The text was updated successfully, but these errors were encountered: