-
Notifications
You must be signed in to change notification settings - Fork 220
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Entity Framework Support #112
Comments
Hello Harry, thanks for creating this issue, natively does not provide any ORM, at this point. Having said that I will create a Product Feature Request in your behalf. Please provide additional information about your use case, the necessity for this, and the implications of lacking native support. I intend to keep the issue open in order to collect as much information as possible, which will let me give feedback to the service team. |
Thanks @tebanieo These capabilities can extend other libraries such MassTransit for outbox pattern integration. At the moment almost all devs have to use 2 separate data sources to use the MassTransit outbox pattern when coupled with DynamodDB, due to no EF Core support. |
Here is an example config that EF Core offers to simply the integration with data sources. These example below highlights how to configure the dbcontext and configure the entity you want to set within the context. This has come from a RD database, but the principal is the same. More than happy to assist with a nosql equivalent. There is a few examples for MongoDb on the web.
|
Will there be support for EF Core with DynamoDb to utilise LINQ expression when querying tables and take advantage of EF Core. MongoDB and CosmosDB is fully supported in EF Core, DynamoDB is the only one left out.
The text was updated successfully, but these errors were encountered: