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

[Question/request] EFCore 7 and 8 support? #2

Open
Kritner opened this issue May 2, 2024 · 5 comments
Open

[Question/request] EFCore 7 and 8 support? #2

Kritner opened this issue May 2, 2024 · 5 comments

Comments

@Kritner
Copy link

Kritner commented May 2, 2024

Glad to see a release version of the package!

The issue

image

EFCore 6 has its end of life later this year (Nov 2024), and there are certainly some perf additions and new features made available in EFCore 7 and 8 that would be great to be able to make use of.

Was curious if there is a plan and/or timeline on shipping a package that can support the newer versions of EFCore

Further technical details

Microsoft.AspNetCore.App version: 8.x

@Kritner
Copy link
Author

Kritner commented Jun 20, 2024

bump? 😅

@stefandevo
Copy link

Why not team up with Pomelo directly. Integrate SingeStore as a dialect in the base repo without doing massive renames of objects? I am sure that a singlestore member can convince the maintainers to integrate Singlestore

@okramarenko
Copy link
Collaborator

hi @Kritner! we are currently working on adding EF 7 support, but, unfortunately, there's no timeline yet.

@okramarenko
Copy link
Collaborator

hi @stefandevo! unfortunately, implementing this solution is more complex than it appears (it's not only massive renames of objects). first, certain functionalities are not supported by SingleStore, and disabling them would require extensive and problematic code modifications. integrating with Pomelo would necessitate numerous hard-coded solutions for foreign keys, referential integrity, unique indexes/constraints, check constraints, savepoints, and other features.

additionally, there are significant differences between MySQL and SingleStore syntax, and syntax plays a critical role in ORM implementation. considering these challenges and the potential code complexity, we have decided to continue adapting our existing solution.

@stefandevo
Copy link

@okramarenko do you have any idea when some updates can be done; in a couple of months EF 8 will be released....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants