node:sqlite alignment regarding api

[halvardssm]

What is the problem this feature will solve?

If you’ve spent any time working with SQL databases in JavaScript, you’ve probably noticed how each database driver has its own way of doing things. Whether you’re connecting to MySQL, PostgreSQL, SQLite, or SQL Server, you’ve had to adapt to different interfaces and quirks. While this diversity showcases the richness of our ecosystem, it can also lead to a lot of headaches. Learning new APIs, dealing with inconsistencies, and maintaining codebases that juggle multiple database drivers can be a real challenge.

What is the feature you are proposing to solve the problem?

Along with database driver maintainers and the deno std team, we have been working on this RFC. What is missing is input from the node team developing the node:sqlite package, and hopefully some shared insight from all parties can be used to create a general base interface that can be implemented across the exosystem. I want to specify that base interface means that it can be extended with methods and options to fit the individual needs of each database, but that the core api stays the same.

What alternatives have you considered?

That the JS ecosystem does not have a unified approach to database interaction.

[RedYetiDev]

IMO the project can't adopt or comment on a non-standard RFC.

CC @cjihrig

[halvardssm]

I fully understand. I just want to make clear that the ultimate goal would be to publish this as a standard. This RFC would be the first step in this direction.

[cjihrig]

the ultimate goal would be to publish this as a standard

To which standards body? SQL itself isn't even consistent among databases.

It seems like this issue is more for raising awareness than anything actionable. Thanks for sharing, but I think we should close this.

[mhdawson]

@halvardssm its not been too actively used yet but this repo was created to try to help the project form positions on standards when appropriate - https://github.com/nodejs/standards-positions

[RedYetiDev]

I don't think this issue is actionable (at least from this repository), so I've closed it. Feel free to reopen.