Skip to content
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

Closed
hikalkan opened this issue Jan 2, 2020 · 1 comment
Closed

Document how to switch to CosmosDB for EF Core #2532

hikalkan opened this issue Jan 2, 2020 · 1 comment
Labels

Comments

@hikalkan
Copy link
Member

hikalkan commented Jan 2, 2020

And also create an integration package like Volo.Abp.EntityFrameworkCore.MySQL if needed.

@yuriy-yarosh
Copy link

yuriy-yarosh commented Aug 14, 2023

@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.

@hikalkan hikalkan removed this from the backlog milestone Aug 27, 2023
@hikalkan hikalkan closed this as not planned Won't fix, can't repro, duplicate, stale Aug 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants