Spring Data MongoDB - Spring Web Services - Parent - SpringSource
Spring Data MongoDB - Spring Web Services - Parent - SpringSource Spring Data MongoDB - Spring Web Services - Parent - SpringSource
please define productname in your docbook file!Query lookup strategiesThe following strategies are available for the repository infrastructure to resolve the query. You canconfigure the strategy at the namespace through the query-lookup-strategy attribute. Somestrategies may not be supported for particular datastores.CREATECREATE attempts to construct a store-specific query from the query method name. The general approachis to remove a given set of well-known prefixes from the method name and parse the rest of the method.Read more about query construction in the section called “Query creation”.USE_DECLARED_QUERYUSE_DECLARED_QUERY tries to find a declared query and will throw an exception in case it can't findone. The query can be defined by an annotation somewhere or declared by other means. Consult thedocumentation of the specific store to find available options for that store. If the repository infrastructuredoes not find a declared query for the method at bootstrap time, it fails.CREATE_IF_NOT_FOUND (default)CREATE_IF_NOT_FOUND combines CREATE and USE_DECLARED_QUERY. It looks up a declared queryfirst, and if no declared query is found, it creates a custom method name-based query. This is the defaultlookup strategy and thus will be used if you do not configure anything explicitly. It allows quick querydefinition by method names but also custom-tuning of these queries by introducing declared queriesas needed.Query creationThe query builder mechanism built into Spring Data repository infrastructure is useful for buildingconstraining queries over entities of the repository. The mechanism strips the prefixes find…By, read…By, and get…By from the method and starts parsing the rest of it. The introducing clause can containfurther expressions such as a Distinct to set a distinct flag on the query to be created. However, thefirst By acts as delimiter to indicate the start of the actual criteria. At a very basic level you can defineconditions on entity properties and concatenate them with And and Or .public interface PersonRepository extends Repository {List findByEmailAddressAndLastname(EmailAddress emailAddress, String lastname);// Enables the distinct flag for the queryList findDistinctPeopleByLastnameOrFirstname(String lastname, String firstname);List findPeopleDistinctByLastnameOrFirstname(String lastname, String firstname);// Enabling ignoring case for an individual propertyList findByLastnameIgnoreCase(String lastname);// Enabling ignoring case for all suitable propertiesList findByLastnameAndFirstnameAllIgnoreCase(String lastname, String firstname);}// Enabling static ORDER BY for a queryList findByLastnameOrderByFirstnameAsc(String lastname);List findByLastnameOrderByFirstnameDesc(String lastname);Example 4.4 Query creation from method namesThe actual result of parsing the method depends on the persistence store for which you create the query.However, there are some general things to notice.1.4.0.BUILD-SNAPSHOTSpring Data MongoDB -Reference Documentation 8
- Page 1 and 2: Spring Data MongoDB - Reference Doc
- Page 3 and 4: please define productname in your d
- Page 5 and 6: please define productname in your d
- Page 7 and 8: please define productname in your d
- Page 9 and 10: please define productname in your d
- Page 11: please define productname in your d
- Page 15 and 16: please define productname in your d
- Page 17 and 18: please define productname in your d
- Page 19 and 20: please define productname in your d
- Page 21 and 22: please define productname in your d
- Page 23 and 24: please define productname in your d
- Page 25 and 26: please define productname in your d
- Page 27 and 28: please define productname in your d
- Page 29 and 30: Part II. Reference DocumentationDoc
- Page 31 and 32: please define productname in your d
- Page 33 and 34: please define productname in your d
- Page 35 and 36: please define productname in your d
- Page 37 and 38: please define productname in your d
- Page 39 and 40: please define productname in your d
- Page 41 and 42: please define productname in your d
- Page 43 and 44: please define productname in your d
- Page 45 and 46: please define productname in your d
- Page 47 and 48: please define productname in your d
- Page 49 and 50: please define productname in your d
- Page 51 and 52: please define productname in your d
- Page 53 and 54: please define productname in your d
- Page 55 and 56: please define productname in your d
- Page 57 and 58: please define productname in your d
- Page 59 and 60: please define productname in your d
- Page 61 and 62: please define productname in your d
please define productname in your docbook file!Query lookup strategiesThe following strategies are available for the repository infrastructure to resolve the query. You canconfigure the strategy at the namespace through the query-lookup-strategy attribute. Somestrategies may not be supported for particular datastores.CREATECREATE attempts to construct a store-specific query from the query method name. The general approachis to remove a given set of well-known prefixes from the method name and parse the rest of the method.Read more about query construction in the section called “Query creation”.USE_DECLARED_QUERYUSE_DECLARED_QUERY tries to find a declared query and will throw an exception in case it can't findone. The query can be defined by an annotation somewhere or declared by other means. Consult thedocumentation of the specific store to find available options for that store. If the repository infrastructuredoes not find a declared query for the method at bootstrap time, it fails.CREATE_IF_NOT_FOUND (default)CREATE_IF_NOT_FOUND combines CREATE and USE_DECLARED_QUERY. It looks up a declared queryfirst, and if no declared query is found, it creates a custom method name-based query. This is the defaultlookup strategy and thus will be used if you do not configure anything explicitly. It allows quick querydefinition by method names but also custom-tuning of these queries by introducing declared queriesas needed.Query creationThe query builder mechanism built into <strong>Spring</strong> <strong>Data</strong> repository infrastructure is useful for buildingconstraining queries over entities of the repository. The mechanism strips the prefixes find…By, read…By, and get…By from the method and starts parsing the rest of it. The introducing clause can containfurther expressions such as a Distinct to set a distinct flag on the query to be created. However, thefirst By acts as delimiter to indicate the start of the actual criteria. At a very basic level you can defineconditions on entity properties and concatenate them with And and Or .public interface PersonRepository extends Repository {List findByEmailAddressAndLastname(EmailAddress emailAddress, String lastname);// Enables the distinct flag for the queryList findDistinctPeopleByLastnameOrFirstname(String lastname, String firstname);List findPeopleDistinctByLastnameOrFirstname(String lastname, String firstname);// Enabling ignoring case for an individual propertyList findByLastnameIgnoreCase(String lastname);// Enabling ignoring case for all suitable propertiesList findByLastnameAndFirstnameAllIgnoreCase(String lastname, String firstname);}// Enabling static ORDER BY for a queryList findByLastnameOrderByFirstnameAsc(String lastname);List findByLastnameOrderByFirstnameDesc(String lastname);Example 4.4 Query creation from method namesThe actual result of parsing the method depends on the persistence store for which you create the query.However, there are some general things to notice.1.4.0.BUILD-SNAPSHOT<strong>Spring</strong> <strong>Data</strong> <strong>MongoDB</strong> -Reference Documentation 8