Workers have outbound TCP connections.
Workers have outbound TCP connections.
ANow, yes. Not last year.
DIt's not so supabase specific, actually. One of their core principles is using existing or their own open source software. In this case it's https://github.com/PostgREST/postgrest
MI mention pgrest in my comment.
DYeah I know, just wanted to throw out there that it's not super specific. Neon also has PostgREST support. 
MNone of the MySQL drivers work (yet) in Workers. You will need a serverless driver and thus a MySQL provider that allows HTTP/WS access - e.g. https://docs.pingcap.com/tidbcloud/integrate-tidbcloud-with-cloudflare
KThere's https://github.com/nora-soderlund/cloudflare-mysql which is https://github.com/mysqljs/mysql adapted by a community member for the TCP Sockets API
KIt has the same downsides as Postgres w/o Hyperdrive
M@nora have you attempted to upstream the sockets support?
MYes.
MGitHub
fast mysqljs/mysql compatible mysql driver for node.js - GitHub - sidorares/node-mysql2: fast mysqljs/mysql compatible mysql driver for node.js
fast mysqljs/mysql compatible mysql driver for node.js - GitHub - sidorares/node-mysql2: fast mysqljs/mysql compatible mysql driver for node.jsMSame as Postgres libs to get SCRAM working. Does yours require
nodejsnode
JLooks like there's some exciting new developments in the Cloudflare dashboard for Hyperdrive 
https://dash.cloudflare.com/?to=/:account/workers/hyperdrive
https://dash.cloudflare.com/?to=/:account/workers/hyperdrive
PI have been spinning wheels on this for a good part of the day. I have HyperDrive (cockroachDB/pg) working with two workers, for whatever reason and I can't figure out what it is, when I run client.connect, it just breaks out of the routine. it doesn't throw an error.
The codes are super duper vanilla:
How do I track this down? It really feels like it has to be config related, but my wrangler files are identical between the three workers.
The codes are super duper vanilla:
How do I track this down? It really feels like it has to be config related, but my wrangler files are identical between the three workers.
MCan you share more details?
- what version of node-Postgres? Definitely the same with both?
- your binding config?
- your hyperdrive config ID?
MHi all. I'm using Hyperdrive with Postgres via
node-postgresclient.query()pool.query()Hey Matt!
Here is the binding config.. The weird thing is that all of the workers are hitting the exact same DB and instance.
I have attached screen shots of the Hyperdrive config.
Here is the binding config.. The weird thing is that all of the workers are hitting the exact same DB and instance.
I have attached screen shots of the Hyperdrive config.
P
MWhy does Wrangler tell me to put the PG connection string (for Hyperdrive use) in my
wrangler.toml.dev.varsWhat is the error message that tells you to do that?
MERROR: In development, you should use a local postgres connection string to emulate hyperdrive functionality. Please setup postgres locally and set the value of "HYPERDRIVE"'s "localConnectionString" to the postgres connection string in your wrangler.toml
MMy dev DB lives on Heroku, so it's a remote DB, not locally-hosted
Mcan you file a feature request for that? https://github.com/cloudflare/workers-sdk/issues/new?assignees=&labels=enhancement&projects=&template=feature-request.yaml&title=%F0%9F%9A%80+Feature+Request%3A
MYou don’t need to manage the pool in the client. Further, because Workers are typically short lived, your “pool” wouldn’t last any longer than your Worker invocation. Hyperdrive’s pooling is much, much more robust.
SLetsgoooo, finally! Thanks team
MWill do.
MGreat! Thanks.
MIs it possible to load one TOML in local dev and another for live? I'm aware that the TOML files supports environments, but I'm trying to circumvent this issue. Guess not if the file must be named exactly
wrangler.tomlyou can pass a path to the config file
MCreate, develop, and deploy your Cloudflare Workers with Wrangler commands.
MAh, interesting
MHi again. My Worker needs to access multiple DBs. Can I set up multiple Hyperdrives under one worker, and how would I model/reference these in the TOML file?
KJust repeat the [[hyperdrive]] block
MRight - and then assign a different value to each
bindingWhen running my worker on CF, for endpoints that talk to Hyperdrive I get an error if I refresh the page soon after getting a response. This seems to happen only for routes that talk to HD, not ones that output a simple, static response. The error is:
A hanging Promise was canceled. This happens when the worker runtime is waiting for a Promise from JavaScript to resolve, but has detected that the Promise cannot possibly ever resolve because all code and events related to the Promise's I/O context have already finished. ✘ [ERROR] Uncaught (in response) Error: The script will never generate a response.Do you have code that reproduces the error?
KIt sounds like you have I/O happening outside of the
fetchIt seems (thanks to @PurpleBlob ) I was reusuing a DB client. I'm in the process of adapting my app from Express.js use, and hadn't properly changed this part to create a DB client on a per-request basis. So all fixed. Thanks anyway.
JI can't wait to try this!
Phey guys - is there a clear docu about localconnectionstring? when i run the worker in local mode it tells me i need to add one - does this string has to be fully text, or can i use env variables in it as well? I really dont like to put passwords in the code.
KIt’s just a string.
Phmm... so now i have it configured exactly like in the example, but when i launch wrangler dev --remote it tells me Unexpected fields found in top-level field: "hyperdrive"
KWhat version is Wrangler?
Pfigured it out - if you never deployed your worker, then its not working. you need to deploy it once to the server, and then the dev --remote works
CYou should log out and back in so wrangler can update its permissions as the message says.