Skip to content

DATAMONGO-952 - Derived query should consider @Query(fields=… #188

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
wants to merge 2 commits into from

Conversation

christophstrobl
Copy link
Member

We check for the presence of field restrictions in the way of single string field name or as json representation in form of { fieldname : 1 } and apply those to the derived query.

Therefore we moved parameter replacement from StringBasedMongoQuery to PartTreeMongoQuery.


Should be back ported to 1.5.x
This one does (though not clean) also applies on 1.4.x.

We check for the presence of field restrictions in the way of single string field name or as json representation in form of { fieldname : 1 } and apply those to the derived query. 

Therefore we moved parameter replacement from StringBasedMongoQuery to PartTreeMongoQuery.
christophstrobl added a commit that referenced this pull request Jun 18, 2014
…@query.

PartTreeMongoQuery now explicitly check the presence of a manually defined field spec on the query method and creates a new Query if so.

Original pull request: #188.
christophstrobl added a commit that referenced this pull request Jun 18, 2014
…@query.

PartTreeMongoQuery now explicitly check the presence of a manually defined field spec on the query method and creates a new Query if so.

Original pull request: #188.
@odrotbohm odrotbohm closed this Jun 18, 2014
@odrotbohm odrotbohm deleted the issue/DATAMONGO-952 branch June 18, 2014 10:55
christophstrobl added a commit that referenced this pull request Jun 20, 2014
…@query.

PartTreeMongoQuery now explicitly check the presence of a manually defined field spec on the query method and creates a new Query if so.

Original pull request: #188.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants