-
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Use standard nitro/db0 layer #7
Comments
Ah true, I forgot it got merged! I'll experiment with this, and probably open one or two PRs to db0 since I see it lacks type support for extensions. I do agree about avoiding fragmenting the ecosystem as much as possible |
@pi0 after opening the PR I just realized that the the clients for each connector isn't exported and I see that is not possible to provide an external instance unjs/db0#19. EDIT: I'm going to open up a related issue about this, IMO is something that could be easily done and I can work on it |
Similar to unstorage, we can expose API to raw client for sure. |
New issue submitted unjs/db0#131, might draft a PR on it later |
Nitro has built-in database layer with pglite support in db0.
While the idea of this module is nice as a full-stack solution, I think this change would really help to avoid fragmenting the ecosystem with several database solutions especially forthe server-side of it.
The text was updated successfully, but these errors were encountered: