Dynamic QueryDSL Projection
I've been using QueryDSL for a while and lately I'm wondering if it's possible to make dynamic projections using the framework, e.g.:
Let's say I have an entity as follows:
public Class User {
private Long id;
private String username;
private String password;
private int age;
private String address;
...Getters and Setters
}
and an endpoint specifying the fields:
http://localhost/users/1?fields=id,username,address
when one fires a get on that address, the expected result would be an object with the id, username, and address properties.
I know a couple of ways of projecting queries using QueryDSL but none includes an 'elegant' solution when dealing with dynamic fields.
querydsl
asked Nov 19 at 16:19
Rafael Sousa
112
add a comment |
I've been using QueryDSL for a while and lately I'm wondering if it's possible to make dynamic projections using the framework, e.g.:
Let's say I have an entity as follows:
public Class User {
private Long id;
private String username;
private String password;
private int age;
private String address;
...Getters and Setters
}
and an endpoint specifying the fields:
http://localhost/users/1?fields=id,username,address
when one fires a get on that address, the expected result would be an object with the id, username, and address properties.
I know a couple of ways of projecting queries using QueryDSL but none includes an 'elegant' solution when dealing with dynamic fields.
querydsl
asked Nov 19 at 16:19
Rafael Sousa
112
add a comment |
I've been using QueryDSL for a while and lately I'm wondering if it's possible to make dynamic projections using the framework, e.g.:
Let's say I have an entity as follows:
public Class User {
private Long id;
private String username;
private String password;
private int age;
private String address;
...Getters and Setters
}
and an endpoint specifying the fields:
http://localhost/users/1?fields=id,username,address
when one fires a get on that address, the expected result would be an object with the id, username, and address properties.
I know a couple of ways of projecting queries using QueryDSL but none includes an 'elegant' solution when dealing with dynamic fields.
querydsl
asked Nov 19 at 16:19
Rafael Sousa
112
I've been using QueryDSL for a while and lately I'm wondering if it's possible to make dynamic projections using the framework, e.g.:
Let's say I have an entity as follows:
public Class User {
private Long id;
private String username;
private String password;
private int age;
private String address;
...Getters and Setters
}
and an endpoint specifying the fields:
http://localhost/users/1?fields=id,username,address
when one fires a get on that address, the expected result would be an object with the id, username, and address properties.
I know a couple of ways of projecting queries using QueryDSL but none includes an 'elegant' solution when dealing with dynamic fields.
querydsl
querydsl
asked Nov 19 at 16:19
Rafael Sousa
112
asked Nov 19 at 16:19
Rafael Sousa
112
asked Nov 19 at 16:19
Rafael Sousa
112
asked Nov 19 at 16:19
Rafael Sousa
112
asked Nov 19 at 16:19
Rafael Sousa
112
112
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
An elegant way (imo) of generating a query from a Request query string is adding @QuerydslPredicate to the method signature in the Controller, as explained here. This gives you a predicate that'll be used in the repository without any extra boilerplate code.
Regarding the result of that query having only the fields that were specified in the query, that could be a job for the client, so it shows only the same fields that were sent.
answered Nov 22 at 17:23
vmaldosan
10828
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53378766%2fdynamic-querydsl-projection%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
An elegant way (imo) of generating a query from a Request query string is adding @QuerydslPredicate to the method signature in the Controller, as explained here. This gives you a predicate that'll be used in the repository without any extra boilerplate code.
Regarding the result of that query having only the fields that were specified in the query, that could be a job for the client, so it shows only the same fields that were sent.
answered Nov 22 at 17:23
vmaldosan
10828
add a comment |
An elegant way (imo) of generating a query from a Request query string is adding @QuerydslPredicate to the method signature in the Controller, as explained here. This gives you a predicate that'll be used in the repository without any extra boilerplate code.
Regarding the result of that query having only the fields that were specified in the query, that could be a job for the client, so it shows only the same fields that were sent.
answered Nov 22 at 17:23
vmaldosan
10828
add a comment |
An elegant way (imo) of generating a query from a Request query string is adding @QuerydslPredicate to the method signature in the Controller, as explained here. This gives you a predicate that'll be used in the repository without any extra boilerplate code.
Regarding the result of that query having only the fields that were specified in the query, that could be a job for the client, so it shows only the same fields that were sent.
answered Nov 22 at 17:23
vmaldosan
10828
An elegant way (imo) of generating a query from a Request query string is adding @QuerydslPredicate to the method signature in the Controller, as explained here. This gives you a predicate that'll be used in the repository without any extra boilerplate code.
Regarding the result of that query having only the fields that were specified in the query, that could be a job for the client, so it shows only the same fields that were sent.
answered Nov 22 at 17:23
vmaldosan
10828
answered Nov 22 at 17:23
vmaldosan
10828
answered Nov 22 at 17:23
vmaldosan
10828
answered Nov 22 at 17:23
vmaldosan
10828
10828
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53378766%2fdynamic-querydsl-projection%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
