-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Document how to switch to CosmosDB for EF Core #2532
Comments
@hikalkan Existing CosmosDB for MongoDB API has certain restrictions and undocumented behaviors, that break certain aggregate queries in an unpredictable manner, so some companies had switched to CosmosDB for NoSQL API and Native CosmosDB driver instead (for EFCore). It worth clarifying if this ticket is for CosmosDB for NoSQL, or CosmosDB for Relational Databases (PostgreSQL + Citus under the hood) ? Also it worth providing proper backwards compatibility layer between CosmosDB for Mongo and CosmosDB for NoSQL, so all the respective collections and indices are properly created, with all the relevant cascading operations. Probably deserve a new ticket and a bit of prior investigation. |
And also create an integration package like Volo.Abp.EntityFrameworkCore.MySQL if needed.
The text was updated successfully, but these errors were encountered: