On using decorator and strategy pattern for dynamically generating SQL queries in JAVA
up vote
0
down vote
favorite
This is a link to my application that actually has the design specified in the image.
The Idea behind the image is that the SubjectInfoViewer behaves as the context in the strategy pattern, and the ViewingQueryComponent behaves as the strategy interface, as well as the component class in the decorator pattern, and its implementing classes except the Filter class are the different strategies. These strategies return an sql string specific to their description, which can be decorated using the Filter class, which is the decorator, in the decorator pattern. The classes implementing the filter class just append the where clause of the sql string produced by the strategies and push the parameters involved in the where clause in a parameter stack, so they can finally by used by a parameterized sql statement involving the whole "stitched" sql string.
For some reason, this doesn't seem to be the right approach to tackle this particular usecase. Kindly suggest the best practices used in this situation.
java sql design-patterns
asked 13 mins ago
Muhammad Luqman
11
New contributor
Muhammad Luqman is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
favorite
This is a link to my application that actually has the design specified in the image.
The Idea behind the image is that the SubjectInfoViewer behaves as the context in the strategy pattern, and the ViewingQueryComponent behaves as the strategy interface, as well as the component class in the decorator pattern, and its implementing classes except the Filter class are the different strategies. These strategies return an sql string specific to their description, which can be decorated using the Filter class, which is the decorator, in the decorator pattern. The classes implementing the filter class just append the where clause of the sql string produced by the strategies and push the parameters involved in the where clause in a parameter stack, so they can finally by used by a parameterized sql statement involving the whole "stitched" sql string.
For some reason, this doesn't seem to be the right approach to tackle this particular usecase. Kindly suggest the best practices used in this situation.
java sql design-patterns
asked 13 mins ago
Muhammad Luqman
11
New contributor
Muhammad Luqman is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
This is a link to my application that actually has the design specified in the image.
The Idea behind the image is that the SubjectInfoViewer behaves as the context in the strategy pattern, and the ViewingQueryComponent behaves as the strategy interface, as well as the component class in the decorator pattern, and its implementing classes except the Filter class are the different strategies. These strategies return an sql string specific to their description, which can be decorated using the Filter class, which is the decorator, in the decorator pattern. The classes implementing the filter class just append the where clause of the sql string produced by the strategies and push the parameters involved in the where clause in a parameter stack, so they can finally by used by a parameterized sql statement involving the whole "stitched" sql string.
For some reason, this doesn't seem to be the right approach to tackle this particular usecase. Kindly suggest the best practices used in this situation.
java sql design-patterns
asked 13 mins ago
Muhammad Luqman
11
New contributor
Muhammad Luqman is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
This is a link to my application that actually has the design specified in the image.
The Idea behind the image is that the SubjectInfoViewer behaves as the context in the strategy pattern, and the ViewingQueryComponent behaves as the strategy interface, as well as the component class in the decorator pattern, and its implementing classes except the Filter class are the different strategies. These strategies return an sql string specific to their description, which can be decorated using the Filter class, which is the decorator, in the decorator pattern. The classes implementing the filter class just append the where clause of the sql string produced by the strategies and push the parameters involved in the where clause in a parameter stack, so they can finally by used by a parameterized sql statement involving the whole "stitched" sql string.
For some reason, this doesn't seem to be the right approach to tackle this particular usecase. Kindly suggest the best practices used in this situation.
java sql design-patterns
java sql design-patterns
asked 13 mins ago
Muhammad Luqman
11
New contributor
Muhammad Luqman is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 13 mins ago
Muhammad Luqman
11
New contributor
Muhammad Luqman is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 13 mins ago
Muhammad Luqman
11
New contributor
Muhammad Luqman is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 13 mins ago
Muhammad Luqman
11
asked 13 mins ago
Muhammad Luqman
11
11
New contributor
Muhammad Luqman is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Muhammad Luqman is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Muhammad Luqman is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Muhammad Luqman is a new contributor. Be nice, and check out our Code of Conduct.
Muhammad Luqman is a new contributor. Be nice, and check out our Code of Conduct.
Muhammad Luqman is a new contributor. Be nice, and check out our Code of Conduct.
Muhammad Luqman is a new contributor. Be nice, and check out our Code of Conduct.
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%2fcodereview.stackexchange.com%2fquestions%2f208432%2fon-using-decorator-and-strategy-pattern-for-dynamically-generating-sql-queries-i%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
