dotnet / dotnet/EntityFramework.Docs

Example contradicts the Warning

Open
#3,997 0 comments 0 reactions 0 assignees View on GitHub
area-query
Dominant language
Mermaid
Stars
1.7k
Forks
2k
Avg merge
7d 23h
Merged PRs (30d)
16

Description

The Warning box explains that it is necessary to specify proper sort order on queries that call `AsSplitQuery()`. Specifically it says "_Note that relational databases do not apply any ordering by default, even on the primary key._"

The example code immediately preceding the warning apparently contradicts this advise. It shows SQL generated from a query that took no care to specify a sort order, yet the generated SQL includes "ORDER BY [b].[BlogId]" in both SELECT statements.

So which is it? Does EF Core do some magic to pick a default sort order or not? Does the SQL in the box really come from the given C# query or not? Something needs to be updated in the document to remove the contradiction.

---
#### Document Details

⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*

* ID: 43baa9f3-c415-c328-6c10-53aabaaec652
* Version Independent ID: 4e789a1b-aa88-d194-dc2e-0a23251250d7
* Content: [Single vs. Split Queries - EF Core](https://docs.microsoft.com/en-us/ef/core/querying/single-split-queries)
* Content Source: [entity-framework/core/querying/single-split-queries.md](https://github.com/dotnet/EntityFramework.Docs/blob/main/entity-framework/core/querying/single-split-queries.md)
* Product: **entity-framework**
* Technology: **entity-framework-core**
* GitHub Login: @smitpatel
* Microsoft Alias: **avickers**

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.