Skip to content

Provide spring data query dsl repository for FactoryExpression with Predicate and Pageable for selecting specified columns [DATACMNS-383] #853

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

Closed
spring-projects-issues opened this issue Oct 16, 2013 · 0 comments
Assignees
Labels
in: repository Repositories abstraction status: declined A suggestion or change that we don't feel we should currently apply type: enhancement A general enhancement

Comments

@spring-projects-issues
Copy link

Rajashekar opened DATACMNS-383 and commented

Please think of following Idea of providing a query dsl repository implementation for selecting specified columns. Presently we have QueryDslPredicateExecutor which allows to load all the records based on Predicate and Pageable.

By extending QueryDslPredicateExecutor implementation think of providing a Repository implementation to select records with specified columns based on FactoryExpression, Predicate and Pageable

For example the repository interface could be something like the following..

public interface QueryDslFactoryExpressionPredicateRepository<T>  	&#123;


    T findOne(FactoryExpression<T> factoryExpression, Predicate predicate);


    Iterable<T> findAll(FactoryExpression<T> factoryExpression, Predicate predicate);


    Iterable<T> findAll(FactoryExpression<T> factoryExpression, Predicate predicate, OrderSpecifier<?>... orders);



    Page<T> findAll(FactoryExpression<T> factoryExpression, Predicate predicate, Pageable pageable);

}


Issue Links:

  • DATAJPA-393 Add support for QueryDSL projections in JPA repositories

4 votes, 5 watchers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: repository Repositories abstraction status: declined A suggestion or change that we don't feel we should currently apply type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

3 participants