Skip to content

Use standard nitro/db0 layer #7

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

Open
pi0 opened this issue Dec 11, 2024 · 4 comments · May be fixed by #8
Open

Use standard nitro/db0 layer #7

pi0 opened this issue Dec 11, 2024 · 4 comments · May be fixed by #8
Assignees
Labels
enhancement New feature or request

Comments

@pi0
Copy link

pi0 commented Dec 11, 2024

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.

@sandros94
Copy link
Owner

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

@sandros94
Copy link
Owner

sandros94 commented Dec 11, 2024

@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.
This greatly limits functionality like Sync, are there any plans? I don't see a related issue/discussion, would you like me to open an issue if it is something that you do plan to support?

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

@pi0
Copy link
Author

pi0 commented Dec 11, 2024

Similar to unstorage, we can expose API to raw client for sure.

@sandros94
Copy link
Owner

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

@sandros94 sandros94 mentioned this issue Dec 13, 2024
10 tasks
@sandros94 sandros94 added the enhancement New feature or request label Feb 20, 2025
@sandros94 sandros94 self-assigned this Feb 20, 2025
@sandros94 sandros94 linked a pull request Feb 20, 2025 that will close this issue
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants