You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's a topic that has been brought up every now and then in the Deno DB community, but as Deno is becoming more stable, supports NPM and Node, and we got JSR, I believe it's time to consolidate and create a db standard SQL interface for TS and JS.
Any input and contribution is greatly appreciated and encouraged as it would be best to make this a collaborative effort amongst the database maintainers since they know the pitfalls for the different engines.
The milestones are as follows:
Decide on an interface for DB clients that can be implemented by any SQL based db. Wrappers can be created for existing database clients to locate potential issues with the interface and current implementations.
Refactor existing databases to implement these interfaces.
The goal for this is to be able to easily transition between databases and have a familiar interface and usage between them.
Consider the PR as a parent issue to have discussions, and where we can finalize the implementation.
The text was updated successfully, but these errors were encountered:
It's a topic that has been brought up every now and then in the Deno DB community, but as Deno is becoming more stable, supports NPM and Node, and we got JSR, I believe it's time to consolidate and create a db standard SQL interface for TS and JS.
I have created a POC in my repo PR.
Any input and contribution is greatly appreciated and encouraged as it would be best to make this a collaborative effort amongst the database maintainers since they know the pitfalls for the different engines.
The milestones are as follows:
The goal for this is to be able to easily transition between databases and have a familiar interface and usage between them.
Consider the PR as a parent issue to have discussions, and where we can finalize the implementation.
The text was updated successfully, but these errors were encountered: