Skip to content

Commit 0c61ad7

Browse files
authored
fixing en-us link
1 parent 63f363f commit 0c61ad7

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/cosmos-db/mongodb-mongoose.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -100,7 +100,7 @@ After you create the database, you'll use the name in the `COSMOSDB_DBNAME` envi
100100

101101
## Best practices for using Mongoose with Cosmos DB
102102

103-
For every model you create, Mongoose creates a new collection. This is best addressed using the [Database Level Throughput option](https://docs.microsoft.com/en-us/azure/cosmos-db/set-throughput#set-throughput-on-a-database), which was previously discussed. To use a single collection, you need to use Mongoose [Discriminators](https://mongoosejs.com/docs/discriminators.html). Discriminators are a schema inheritance mechanism. They enable you to have multiple models with overlapping schemas on top of the same underlying MongoDB collection.
103+
For every model you create, Mongoose creates a new collection. This is best addressed using the [Database Level Throughput option](set-throughput.md#set-throughput-on-a-database), which was previously discussed. To use a single collection, you need to use Mongoose [Discriminators](https://mongoosejs.com/docs/discriminators.html). Discriminators are a schema inheritance mechanism. They enable you to have multiple models with overlapping schemas on top of the same underlying MongoDB collection.
104104

105105
You can store the various data models in the same collection and then use a filter clause at query time to pull down only the data needed. Let's walk through each of the models.
106106

0 commit comments

Comments
 (0)