Connector support tracker

[pi0]

Supporting SQL(lite) connectors for db0 is almost straightforward forward and by having platform/vendor connectors, we take the pain away from end-users for (almost) zero config experience. Using this issue to keep track of possible connectors in the roadmap:

• Cloudflare D1 (docs)
• LibSQL (docs)
• PostgresSQL (docs)
• Better SQLite3 (docs)
• Bun sqlite (docs)
• Planetscale (docs)
• Mysql (docs)
• Vercel PosgresSQL (docs, based on neon)
• Deno @db/sqlite (docs)
• Neon (docs)
• Turso (docs, based on libSQL)
• Capacitor (docs)
• Cordova (docs)
• SurrealDB (docs)
• dolt (docs)

[moshetanzer]

suposing you didnt add some of these connectors to docs on purpose? Or shoudl they be added with planned message?

[vinayakkulkarni]

I'd also would love to add multiple connectors to Postgres, ~ to lucia-auth.com

[pi0]

@moshetanzer only native(app) ones wasn't sure to list for now if anything else missing feel free to make PR.

@vinayakkulkarni Surely we can support postgres to but I'm curious any specific reason you would prefer it over pg? my first impression is that pg has much more downloads and even cloudflare TCP variant.

[alex-eri]

maybe ODBC?

[MickL]

Would LOVE to see Vercel Postgres and Neon :)

[MertcanYuzer]

MSSQL support would be awesome

[vinayakkulkarni]

@moshetanzer only native(app) ones wasn't sure to list for now if anything else missing feel free to make PR.

@vinayakkulkarni Surely we can support postgres to but I'm curious any specific reason you would prefer it over pg? my first impression is that pg has much more downloads and even cloudflare TCP variant.

I tried postgres, pg & the neon one but seems only postgres pkg is the one that works for.

Error: Cannot resolve "cloudflare:sockets" from "/home/runner/work/vinayakkulkarni.dev/vinayakkulkarni.dev/node_modules/postgres/cf/polyfills.js" and externals are not allowed!

1. Tried deploying on deno deploy, got the above error, see the workflow –https://github.com/vinayakkulkarni/vinayakkulkarni.dev/actions/runs/8592876841/job/23543545906
2. Tried deploying on CF worker as well but that failed too, lemme find the workflow which failed to deploy on CF
3. Only using postgres pkg & Vercel NITRO_PRESET=vercel worked for me

[vinayakkulkarni]

Related issue(s):

• Bundling of dependency pg fails for workers preset because it bundle the optional dependency pg-native. Is there a way to ignore this ? nitrojs/nitro#178
• Cloudflare pages deployment issue nitrojs/nitro#1679
• CommonJS error when trying to import { Pool } from 'pg' nitrojs/nitro#73
• Postgres connector: The requested module 'pg' does not provide an export named 'Client' #62

[sandros94]

I'm curious to understand something: for an HTTP only connector (in particular I'm talking about SurrealDB), is it enough to create an ofetch and map the various RPC endpoints?

If this is the case I would like to help with that one, considering the knowledge I've gathered while writing nuxt-surrealdb module

[reslear]

for capacitor looks good

[Kampouse]

am trying the latest with libsql and get this

[justserdar]

We could revive my old PR to db0 for Turso and Drizzle.

#64

@pi0 you might remember my PR, it might be outdated atm
@sandros94 Any idea's?