Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
For every RavenDb Index field I can specify Storage, Sorting, Indexer and Analyzer. In which cases should I use / not use these attributes?
I tried to find detailed description of these attributes but didn’t succeed.
There is good documentation available here: http://ravendb.net/docs/client-api/querying/static-indexes/configuring-index-options
As for when to use / not to use them: as your needs demand. Most of the the time, you don’t need to create a static index on your own and can just rely on RavenDBs ability to create an indexes dynamically based on your queries. However, if you want to do stuff like full text searching, field storage or map/reduce indexes you will need to define a static index upfront.