Provider-agnostic timeouts

Open
#18,456 2 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
28/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
databases

Research direction

Start by reviewing the existing provider-specific command and connection timeout APIs, then read the discussion in #6080 about in-memory behavior. Done means a core database-access timeout can be configured, providers can map it to their lower-level timeouts, and provider-specific settings still override it.

Written by the indexing model from the issue text.

Description

area-dbcontext

The idea here is to have a core-level API to set a "database access timeout". Every provider would then use the value set to configure appropriate timeouts in the lower-level APIs that the provider uses. For example, a relational provider would use this to set both command and connection timeouts.

Any call to a more provider-specific API would override anything set here.

This has two advantages:

  • It avoids confusion caused by multiple, subtly different timeouts--e.g. command verses connection
  • It allows the in-memory database to either ignore or implement timeouts as appropriate without being a relational provider--see #6080
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.