-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Idea: WebSQL Provider (Sqlite on Blazor) #10999
Comments
@grahamehorner This is an interesting idea that has been discussed recently, but we're not 100% sure that EF is a good fit here. Assigning to @divega to follow up more. |
@ajcvickers understand, the reason for asking was that IMHO if EF Core was able to target WebSQL within Blazor/Mono wasm runtime this would bring a great benefits to the developer have aligned data access in both client/server and allow client side caching of data and possibly offline functionality. |
Very useful for electron apps, where frontend size is not big issue. |
Here are some initial thoughts on this (based on a conversations with @SteveSandersonMS): Reasons EF Core may not be a good fit for Blazor:
Reasons EF Core may be a good fit for WebSQL:
Regardless, we may want to have an EF Core-like experience for Blazor. We will keep this issue in the backlog, waiting to learn more. |
I'm not sure if it helps, but github has various examples of modern SQLite compiled to WebAssembly. If that is functional, WebSQL Provider wouldn't be necessary. |
can you recall that example link please? I am looking for the Blazor webassembly with sqlite (without .net core hosted). |
See also #18908 |
Note from triage: we don't plan to support this directly in EF Core, but we do want to support/enable external efforts to compile and use SQLite in WASM. |
now that the blazor project is an official research project at Microsoft please consider creating a client side entity framework core provider for WebSQL so that blazor client can work with local data storage and utilise the power of entity framework core, linq etc.
The text was updated successfully, but these errors were encountered: