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

Idea: WebSQL Provider (Sqlite on Blazor) #10999

Closed
grahamehorner opened this issue Feb 16, 2018 · 8 comments
Closed

Idea: WebSQL Provider (Sqlite on Blazor) #10999

grahamehorner opened this issue Feb 16, 2018 · 8 comments

Comments

@grahamehorner
Copy link

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.

@ajcvickers
Copy link
Contributor

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

@grahamehorner
Copy link
Author

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

@HalidCisse
Copy link

Very useful for electron apps, where frontend size is not big issue.
Electron + blazor + EfCore = ?

@divega
Copy link
Contributor

divega commented Mar 12, 2018

Here are some initial thoughts on this (based on a conversations with @SteveSandersonMS):

Reasons EF Core may not be a good fit for Blazor:

  • Size constraints: I don't know what the effective constraints are, but perhaps @SteveSandersonMS can provide some more information. Presumably this maybe less of an issue for Electron apps (as mentioned above in the thread)?
  • Reliance on executing LINQ expressions that are compiled and cached at run-time, which Blazor may not be efficient at

Reasons EF Core may be a good fit for WebSQL:

  • We already have a Sqlite provider, so this should at least be less work than IndexDB

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.

@divega divega modified the milestones: 2.1.0, Backlog Mar 12, 2018
@divega divega removed their assignment Mar 12, 2018
@divega divega changed the title idea: WebSQL Provider Idea: WebSQL Provider (Sqlite on Blazor) Mar 12, 2018
@mpaine-act
Copy link

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.

@970065574
Copy link

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

@bricelam
Copy link
Contributor

bricelam commented Jan 2, 2020

See also #18908

@ajcvickers
Copy link
Contributor

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.

@ajcvickers ajcvickers removed this from the Backlog milestone Oct 27, 2021
@ajcvickers ajcvickers reopened this Oct 16, 2022
@ajcvickers ajcvickers closed this as not planned Won't fix, can't repro, duplicate, stale Oct 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants