Moving The Repo: Grouping DB Drivers

[ebebbington]

Hey! :) I've been speaking about db drivers for deno in the deno discord, and thought it might be a good idea to have a single org to hold all db drivers, eg deno_db_drivers/postgres, .../mongo, .../sql, ../sqlite. I was curious on how you felt about moving your sqlite repo? The idea came about as the mongo driver for deno is unmaintained now (and a deno plugin so very unstable), and there's a few people saying 'oh i can't do it, it's too much work', so i intend on getting a team together as if we all realise there's plenty of people that want to, then we can start. And the mongo driver would be porting mogodb's node port. Then it'd be amazing if all db drivers were under a single roof.

Of course i wouldn't be the leader for the org, we (and the other driver authors) would be, and i have no intention on stopping development within the deno community

The end result is the deno community can develop stable drivers

Let me know what you think :)

Thanks, Edward

[dyedgreen]

Hey!

Yes, I believe that generally this could be a good idea, as it allows everyone to share some of the maintenance burden and responsibility. Have you reached out to the maintainers of the other DB drivers out there, to see what they think about something like this?

[ebebbington]

Thanks for the response, and yes, @hayd the maintainer (and new owner) of postgres has said he is happy to move the repo, then of course we have a non-deno-plugin db driver under the org. I have asked the author of SQL too but no response as of yet, and i am going to ask the author of deno_redis too.

So to put it into perspective:

• mongodb
• Postgres
• sqlite
• sql
• redis
• pgc4d (there are talks about asking the author)

If you'd prefer, i can see if i can get the others on board before you commit to anything? We have teams under the org and discord channels (a new discord group was created) for each repo, so the level of permissions can be kept strict and you would still be the owner of sqlite

[ebebbington]

Wait, scratch sql, i'm getting myself confused and think it is only a query builder - trying to juggle too many things at the moment 😆

[ebebbington]

Author of MySQL is on board as well, leaving Redis and possibly pgc4d

[ebebbington]

Org link: https://github.com/denodrivers
Discord: https://discord.gg/r5WZ485

[dyedgreen]

Sounds good! Let's see what everyone else is saying before starting to move things around, but I think I'm pretty happy with having MongoDB, Postgress, and SQLite under one roof already.

[ebebbington]

And mysql :) That's all (or one of each) of the db drivers, join the discord if you want and then we can chat easier and the team/channel(s) can be created

[ebebbington]

Redis now too 🎉

Just give me the OK whenever you want and i'll set up the GH team and discord channels :)

[dyedgreen]

That's great news! 🥳

I'm currently still super busy with exams, but I'll get back to you when they finish 😅

[dyedgreen]

Just wanted to update this thread, since nothing happened for more than a year:

Since this issue was opened, I was approached a few times by @biwanczuk about plans to move the WASM SQLite wrapper into the deno std library. I think this is probably a good idea (e.g. Python also includes SQLite in it's standard library, and Deno's standard library is versioned, which resolves some of the issues that come with having to commit to a sub-optimal interface for backwards comparability reasons).

Until there is some more clarity around what will / should happen with respect to this, I wanted to hold off moving anything around, to prevent needless churn for people working on / using this library.

[sant123]

Moving this repository to the Deno std sounds awesome!!! @dyedgreen have you received any news? Hope this is still on plans @bartlomieju 🙏🏼