Skip to content

Commit 3aa35d3

Browse files
p-mongop
andauthored
MONGOID-4904 Use a generic client name in tutorial example rather than "secondary" (#4792)
Co-authored-by: Oleg Pudeyev <[email protected]>
1 parent deb78a5 commit 3aa35d3

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

source/tutorials/mongoid-documents.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ in from the defaults.
5252

5353
class Person
5454
include Mongoid::Document
55-
store_in collection: "citizens", database: "other", client: "secondary"
55+
store_in collection: "citizens", database: "other", client: "analytics"
5656
end
5757

5858
The ``store_in`` macro can also take lambdas - a common case for this is multi-tenant applications.

source/tutorials/mongoid-persistence.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -552,7 +552,7 @@ Model-Level Persistence Options
552552

553553
On a per-model basis, you can tell it to store in a custom collection name, a different
554554
database, or a different client. The following example would store the Band class by
555-
default into a collection named "artists" in the database named "music", with the client "secondary".
555+
default into a collection named "artists" in the database named "music", with the client "analytics".
556556

557557
Note that the value supplied to the ``client`` option must be configured under ``clients``
558558
in your mongoid.yml.
@@ -561,7 +561,7 @@ in your mongoid.yml.
561561

562562
class Band
563563
include Mongoid::Document
564-
store_in collection: "artists", database: "music", client: "secondary"
564+
store_in collection: "artists", database: "music", client: "analytics"
565565
end
566566

567567
If no ``store_in`` macro would have been provided, Mongoid would store the model in a

0 commit comments

Comments
 (0)