From 057a6529b073eaab6cfb33c0826ed80e322e82a6 Mon Sep 17 00:00:00 2001 From: AndriySvyryd Date: Wed, 4 Nov 2020 12:56:17 -0800 Subject: [PATCH] Update Cosmos cross-partition limitation Fixes #2816 --- entity-framework/core/providers/cosmos/limitations.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/entity-framework/core/providers/cosmos/limitations.md b/entity-framework/core/providers/cosmos/limitations.md index 91bd496843..67cee658e6 100644 --- a/entity-framework/core/providers/cosmos/limitations.md +++ b/entity-framework/core/providers/cosmos/limitations.md @@ -2,7 +2,7 @@ title: Azure Cosmos DB Provider - Limitations - EF Core description: Limitations of the Entity Framework Core Azure Cosmos DB provider as compared to other providers author: AndriySvyryd -ms.date: 11/05/2019 +ms.date: 11/05/2020 uid: core/providers/cosmos/limitations --- # EF Core Azure Cosmos DB Provider Limitations @@ -26,4 +26,4 @@ The Cosmos provider has a number of limitations. Many of these limitations are a You can see the full overview of [Azure Cosmos DB supported features](/azure/cosmos-db/modeling-data), these are the most notable differences compared to a relational database: - Client-initiated transactions are not supported -- Some cross-partition queries are either not supported or much slower depending on the operators involved +- Some cross-partition queries are slower depending on the operators involved (for example `Skip/Take` or `OFFSET LIMIT`)