Update type mapping/converters to make translation data available for query generation

Open
#15,979 0 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
databases

Research direction

Begin with the linked issue and planning comment, then trace type mappings and value converters into query generation. Done means ordering metadata is available, non-order-preserving conversions reject the listed order-based operations, and an API permits explicitly allowing them.

Written by the indexing model from the issue text.

Description

area-o/c-mapping area-query

From https://github.com/aspnet/EntityFrameworkCore/issues/10265#issuecomment-458357654

Notes from planning:

  • We will add ordering metadata to value conversions, which will then be available on the type mapping
  • If conversion is not order-preserving, then we throw if an order-based operation is used.
    • For example less than, greater than, min, max.
    • This could include order-by, but note, that commonly any fixed ordering can fine.
  • Add API to allow these operations anyway
Dominant language
C#
Stars
14.8k
Forks
3.4k
Avg merge
2d 5h
Merged PRs (30d)
134

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/efcore

All issues in dotnet/efcore

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.