From 9940712a039c74fced8d9d5b513cf0c628507008 Mon Sep 17 00:00:00 2001
From: Luke Latham <1622880+guardrex@users.noreply.github.com>
Date: Mon, 7 Oct 2024 05:02:27 -0400
Subject: [PATCH] SQLite doesn't support automatic concurrency (#33800)

---
 aspnetcore/blazor/blazor-ef-core.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/aspnetcore/blazor/blazor-ef-core.md b/aspnetcore/blazor/blazor-ef-core.md
index 2e700fd342..1e79be74bd 100644
--- a/aspnetcore/blazor/blazor-ef-core.md
+++ b/aspnetcore/blazor/blazor-ef-core.md
@@ -44,7 +44,9 @@ For Microsoft Azure services, we recommend using *managed identities*. Managed i
 
 ## Sample app
 
-The sample app was built as a reference for server-side Blazor apps that use EF Core. The sample app includes a grid with sorting and filtering, delete, add, and update operations. The sample demonstrates use of EF Core to handle optimistic concurrency.
+The sample app was built as a reference for server-side Blazor apps that use EF Core. The sample app includes a grid with sorting and filtering, delete, add, and update operations.
+
+The sample demonstrates use of EF Core to handle optimistic concurrency. However, [native database-generated concurrency tokens](/ef/core/saving/concurrency?tabs=fluent-api#native-database-generated-concurrency-tokens) aren't supported for SQLite databases, which is the database provider for the sample app. To demontrate concurrency with the sample app, adopt a differnt database provider that supports database-generated concurrency tokens (for example, the [SQL Server provider](/ef/core/providers/sql-server)).
 
 :::moniker range=">= aspnetcore-8.0"