search

dotnet / efcore

EF Core is a modern object-database mapper for .NET. It supports LINQ queries, change tracking, updates, and schema migrations.
https://docs.microsoft.com/ef/
MIT License
13.63k stars 3.15k forks source link

Azure Table Storage Provider #1142

Open rowanmiller opened 9 years ago

rowanmiller commented 9 years ago

Parent item to track finishing this provider once we have the core of EF7 padded out and stabilized.

wangkanai commented 8 years ago

As the Core coming to RC. How would Azure Table Storage provider start to kick in development?

Aanhane commented 8 years ago

Any update on this? I'm really looking forward to implement Table Storage with EF Core!

venkatesh-bhupathi commented 7 years ago

Any update on this? Any timelines for making this available as released component?

rowanmiller commented 7 years ago

@venkatesh-bhupathi The provider is currently on-hold as our team focuses on adding in the critical features that prevent folks from adopting EF Core. We do plan to bring the provider back and RTM it, but we don’t have a timeframe at this stage.

divega commented 7 years ago

Consider issues #1187, #961 and #458.

guardrex commented 7 years ago

Does the addition of the propose-close label mean that you've decided to never support ATS in EF Core?

ajcvickers commented 7 years ago

@guardrex The "propose-close" label is something that can be added by members of the EF team to suggest we should revisit this item to see whether or we should continue to keep this issue on the backlog. It doesn't mean we have decided to close it yet.

In this case, we may close the issue because things have moved forward in the last couple of years to a place where a Cosmos DB provider may have much more value than an ATS provider, and if the trend continues it may be that ATS is never high enough priority for our team to implement. That doesn't prevent a community driven effort to create a provider, such as is the case for many other database back-ends.

ajcvickers commented 6 years ago

Closing this as we are focusing our efforts on Cosmos DB (initially as a document store) rather than ATS. We don't intend for the EF team to implement and maintain an ATS provider, but we would be fully supportive of community efforts to do so.

MisinformedDNA commented 6 years ago

Adding link for reference: Writing a Database Provider

MisinformedDNA commented 6 years ago

@ajcvickers Since ATS and Cosmos Tables share the same API, I presume this means you aren't creating an EF provider for Cosmos Tables either. Is that right?

ajcvickers commented 6 years ago

@MisinformedDNA It's not currently in our plans.

ajcvickers commented 2 years ago

Re-opening to discuss in triage since other sources indicate there is still some demand for this.

OzBob commented 1 year ago

If @MisinformedDNA is correct then, would the experiment be to implement the CosmosDB EF provider and provide a connection string to the Azure Table Storage (ATS)?

ErikEJ commented 1 year ago

@OzBob it is two different SDKs

bakes82 commented 1 year ago

@OzBob it is two different SDKs

@ErikEJ azure tables is both. “The Azure Tables client library can seamlessly target either Azure Table storage or Azure Cosmos DB table service endpoints with no code changes. “ I haven’t tried to connect to ast via a cosmos ef connection to know if they are different but the base api is shared between the two. Maybe like @OzBob says it’s a slightly diff connection format change and use the Cosmos implement.