From 88d87804d4ab0478c76ec983a1c50963eca81d6c Mon Sep 17 00:00:00 2001
From: Alex Reisner <alex@alexreisner.com>
Date: Thu, 18 Jul 2013 06:24:06 -0400
Subject: [PATCH] Clean up language and spacing.
---
README.md | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/README.md b/README.md
index 6abc59f2..9886b857 100644
--- a/README.md
+++ b/README.md
@@ -742,14 +742,15 @@ Known Issue
You cannot use the `near` scope with another scope that provides an `includes` option because the `SELECT` clause generated by `near` will overwrite it (or vice versa).
-Instead of using `includes` to reduce the number of database queries, try using `joins` with either the `:select` option or a call to `preload`. Both choices are demonstrated below:
+Instead of using `includes` to reduce the number of database queries, try using `joins` with either the `:select` option or a call to `preload`. For example:
# Pass a :select option to the near scope to get the columns you want.
# Instead of City.near(...).includes(:venues), try:
City.near("Omaha, NE", 20, :select => "cities.*, venues.*").joins(:venues)
-
- # This preload call will normally trigger 2 queries regardless of the number of results; one query
- # on hotels, and one query on administrators. Instead of Hotel.near(...).includes(:administrator), try:
+
+ # This preload call will normally trigger two queries regardless of the
+ # number of results; one query on hotels, and one query on administrators.
+ # Instead of Hotel.near(...).includes(:administrator), try:
Hotel.near("London, UK", 50).joins(:administrator).preload(:administrator)
If anyone has a more elegant solution to this problem I am very interested in seeing it.
--
GitLab