Skip to content

Fixed "retail" being swapped with "MongoDB" #194

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Sep 6, 2012
Merged

Fixed "retail" being swapped with "MongoDB" #194

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions source/use-cases/product-catalog.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -360,8 +360,8 @@ order of the index does not matter.
.. note::

If you want to preform range queries (e.g. "return all products
over $25") and then sort by another property like ``pricing.MongoDB``,
retail cannot use the index as effectively in this situation.
over $25") and then sort by another property like ``pricing.retail``,
MongoDB cannot use the index as effectively in this situation.

The field that you want to select a range, or perform sort
operations, must be the *last* field in a compound index in order
Expand Down